Netlify Related: Google Font error - CORS policy: Cross origin requests are only supported

Support
,
1

URGENT. I’m spending advertising money on this site.

I have an odd problem. I’m getting console errors in Chrome and am unable to load my google fonts:

Access to font at ‘about:blank’ (redirected from ‘https://fonts.gstatic.com/s/ubuntu/v14/4iCv6KVjbNBYlgoCxCvjsGyNPYZvgw.woff2’) from origin ‘https://www.larsxn.com’ has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https.

This problem only occurs when I access my site from production: www.larsxn.com.

The font problem does not exist when you access the website here:
https://5edc72971bc8620008178a3b--determined-mirzakhani-53692a.netlify.app/

And the font problem does not exist here on github pages:
https://clarson10024.github.io/Larsxn_Music/index.html

I am using (after reviewing this forum) netlify.toml with the following:

The following redirect is intended for use with most SPAs that handle

routing internally.

[[redirects]]
from = “/*”
to = “/index.html”
status = 200

[[headers]]

Define which paths this specific [[headers]] block will cover.

for = “/"
[headers.values]
Access-Control-Allow-Origin = "”

And _headers with:

/*
Access-Control-Allow-Origin: *

Here is my deploy log:

12:52:39 AM: Build ready to start
12:52:41 AM: build-image version: 30f629161c0736b1a3ecd8b418e5eeffab5c0faf
12:52:41 AM: build-image tag: v3.3.14
12:52:41 AM: buildbot version: 960d989224ecbd0e01be03c5f7dffe3d8f543e02
12:52:41 AM: Fetching cached dependencies
12:52:41 AM: Starting to download cache of 53.0MB
12:52:42 AM: Finished downloading cache in 455.242803ms
12:52:42 AM: Starting to extract cache
12:52:42 AM: Finished extracting cache in 551.042103ms
12:52:42 AM: Finished fetching cache in 1.020157548s
12:52:42 AM: Starting to prepare the repo for build
12:52:43 AM: Preparing Git Reference refs/heads/master
12:52:45 AM: No build command found, continuing to publishing
12:52:45 AM: Starting to deploy site from ‘/’
12:52:45 AM: Creating deploy tree
12:52:45 AM: Creating deploy upload records
12:52:45 AM: 2 new files to upload
12:52:45 AM: 0 new functions to upload
12:52:45 AM: Starting post processing
12:52:46 AM: Post processing done
12:52:46 AM: Site is live
12:52:48 AM: Finished processing build request in 7.296977842s

When I press the ‘Preview’ button above my log, I’m taken to this site where the fonts are fine:

Please see the reference to the Netlify site above.

However, when I press the ‘Preview Deploy’ link on the Published Deploy tab, I go to the production version of my website where the font problem exists and I get see the error message in the Chrome console.

I had google analytics, google tag manager, and FaceBook pixel snippets, but all have been commented out.

Fortunately, this problem is limited to Chrome and ios and safari version show the correct fonts. But the site looks awful on Chrome. I’ve spent hours on this, and the problem must somehow be related to the Netlify deployment. I am using my own domain, mentioned above. I have not had font problems in the past week. This appears to be new.

Any help you can give me will be greatly appreciated. My site looks awful.

2

I’m not sure that our service was the root cause here, @clarson10024, but I be happy to research this.

If your site has a CORS policy, you define it. We don’t enforce one by default. Would you please let us know what your CORS policy was when these error occurred?

Also, I’m not able to reproduce the issue currently. The custom domain URL is a 404 currently.

Without being able to see the issue myself, it is hard for me to research (or even guess) what the root cause was. Based on the error itself it sounds like something redirected the font request to ‘about:blank’. If so, that would be something in the site code not at the server.

Would you please send us a link to some page or site which reproduces this issue? Or would you be willing to revert to the previous configuration so we can test it?

If there are questions for us, please let us know.

3

Luke, thanks for following up. I would have addressed this myself earlier, but I didn’t think my post was logged. Couldn’t find a record of it after I hit submit.

At any rate, this turned out to be a Google Ad Tag problem. When I removed the snippets, and cleared my browser cache, the problem went away.

Thanks again,
Chris