Icons and images don't show on the website anymore which makes voting quite difficult
Access to font at 'https://assets2.pollunit.com/packs/media/fonts/pollunit-59af44c8899b307fac23f3b800ae507f.woff' from origin 'https://pollunit.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
pollunit-59af44c8899b307fac23f3b800ae507f.woff:1
Any change to fix this?
Thanks
Hi Matthieu,
Does the problem still persist?
Kind regards
Philipp
Hi Philipp, yes, this problem is still present on both Chrome and Firefox.
You need to look at your asset server configuration and allow pollunit.com to load the assets from assets2.pollunit.com. Here's a guide https://stackoverflow.com/questions/10636611/how-does-access-control-allow-origin-header-work
It seems that on your assets2.pollunit.com server you must add a header for the font files:
Access-Control-Allow-Origin: https://pollunit.com
It might be that your Nginx server is serving the fonts and not your app server, so that's why your JS loading works and not your fonts.
Here's the error I am seeing
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://assets2.pollunit.com/packs/media/fonts/pollunit-59af44c8899b307fac23f3b800ae507f.woff. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200
Looks like you've fixed it!
Thank you! I think it was a caching problem with our staging server, which has the same assets.
Hi. My participants have the exact same problem again: the icons don't show anymore. Once I call the woff font file directly, then it works. Any chance you can fix this?
Hi Bernhard,
we could not reproduce the problem. However we invalidated the cache. Can you try now again (Maybe also clear your browser cache).
If it does not work, is the problem maybe because you are inside a corporate network?
Kind regards
Philipp
Hi Philipp, thanks for the prompt reaction. It seems that it is fixed now.
How it can be, that you can't reproduce it, I'm not sure. First I thought it was a local problem on my machine, until my participants had the exact same problem. Maybe it was a local problem just in Switzerland on some proxy servers?
On my phone I still have the problem just for the home page https://pollunit.com/de
Anyway, I'm not sure if this helps: to me it seemed as if the problem occured after I switched the layout of the poll a few times in quick succession. Is it possible, that I alone can crash the cache?
cheers, Bernie
It is weird and we do not understand it yet. Our fonts are in the aws cloudfront cache and this can be locally (for instance In Switzerland) different.