CORS problems with Mobile only

support
1

Hello,

My website (https://bobadams5.com) was built with the newest hugo (0.104) and the newest update of the hugo-clarity theme. For some reason I have CORS errors on mobile although the site works fine from a desktop. My config.toml baseurl is set to “https://www.bobadams5.com”

Can someone help? This has been driving me nuts.

The errors I get are:
Access to CSS stylesheet at 'https://www.bobadams5.com/css/styles.17bd8db1e1e9d3fde7e52431779c901a12c654a66914bb4472fd4b0c6880c72ea87f9dc818f7ca35bf2e934c65a6a7d6c7afa12a18e60a79ff4e093e3ac621ba.css' from origin 'https://bobadams5.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. bobadams5.com/:45 GET https://www.bobadams5.com/css/styles.17bd8db1e1e9d3fde7e52431779c901a12c654a66914bb4472fd4b0c6880c72ea87f9dc818f7ca35bf2e934c65a6a7d6c7afa12a18e60a79ff4e093e3ac621ba.css net::ERR_FAILED 200 bobadams5.com/:1 Access to script at 'https://www.bobadams5.com/en/js/bundle.7a4f5ee897116484f0e69a8f45895cbc1e5f2ebb542f9565f11784c7e01a453383ee5ce48dc539996bb6b8d2ff3a26870376b2760b6073ef581d4a5da24987af.js' from origin 'https://bobadams5.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. bobadams5.com/:50 GET https://www.bobadams5.com/en/js/bundle.7a4f5ee897116484f0e69a8f45895cbc1e5f2ebb542f9565f11784c7e01a453383ee5ce48dc539996bb6b8d2ff3a26870376b2760b6073ef581d4a5da24987af.js net::ERR_FAILED 200 bobadams5.com/:1 Access to manifest at 'https://www.bobadams5.com/icons/site.webmanifest' from origin 'https://bobadams5.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. www.bobadams5.com/icons/site.webmanifest:1 GET https://www.bobadams5.com/icons/site.webmanifest net::ERR_FAILED 200

2

Your site is available in two locations:

Pick one, and redirect the other. Your baseURL should match.

1 Like
3

Thank you!

I feel silly finding such a simple solution, but I think it was because I was debugging on mobile with Chrome for the developer options, but I use Brave on desktop which has some automatically upgrade to https and other features enabled that was probably adding the www for me.

4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.