As of today, I’m noticing that Google Chrome is blocking our fonts that we added ourselves in Sitejet.
In DevTools the following error message appears:
Until now, the fonts have always loaded correctly.
We use some of the same fonts in other builders. Here the fonts are not blocked.
So it seems to be a problem of Sitejet …
Does anyone know what to do here?
Hello, I can confirm this is the case for the latest version of Chrome on Mac also. Either with Google Fonts or with fonts you manually upload into SiteJet.
Same error including “has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.”
I saw this issue when testing in Chrome during the 404 issue reported earlier today with Collections. But thought that was my cache. I have since gone on and have started testing with Chrome (I usually use Safari for my sins), and the same issue is occuring.
Many thanks,
Lee
Mate I’ve pinged them on this ticket also. They resolved the 404 at least for my sites but I realised the font issue is affecting sites for me also. Their 404 issue on Collections is still present on their corporate site so you may wish to check yours?
@Lee_Jackson / @Patrick_Luescher
We have forwarded this yesterday to your developers to find the source of this and resolve it. However, just to check in - does this error still occur at the moment? We are unable to reproduce it at the moment.
Hi Buddy,
Yes still happening for me when using a WOFF file uploaded to SiteJet. I had the same issue if I switched to a Google Font. Here’s a screenshot which should give you everything you need:
Cheers bud,
Lee
Cheers! Will forward this to the developers!
Hi! I’ve tested this, and is still happening … some requests go through … but most of them fail with … CORS error …
I’ve recorded a video with the issue.
@Lucian_Dinu @Lee_Jackson @Patrick_Luescher Could you send us the IDs of the websites where it occurs, please.
Fastest way would be my DM here for this case.
Sent direct mate. Thank you!
Thank you, André! I have sent you some projects.
Hey there, the situation has been rectified on the server side. Please clear your browser cache just in case. Thank you very much for your patience. 
It works now. Thank you!
Thank you! 
