CF Pages: updating page via gh push adds CORS issues, breaks audioplayback / file serving
Hello, when I pushed a new update today after a while to our website via GH/CF Pages, the sites audio playback stopped working and many cors SHA256 errors pop up in the console. What could the reason for this be? It can't be general file hosting issues I think, cause our 3D models and images download fine.
I'm not the one who set this cf workflow up, so I don't know what could be causing this.
Any tips appreciated
3 Replies
I found others with the same issue online mentioning cf, they said redeploying helps and that it's a rare issue or smt, but I tried reverting and redeploying and the came back again
People often get confused with Pages asset retention cache and custom domains cache.
Easiest way to exclude that is: Do you get the same issue on your pages.dev preview url?
Ignore those sha errors, it's about CF insights which doesn't matter if it fails
It doesn't work on either site.pages.dev or site.com
but the build works when I tested it locally before deploying
The music files are accessible, so it's just some specific js that doesn't work for some reason...
Okay I think the culprit is using npm on CF and pnpm to build locally
remember to add an appropriate
PNPM_VERSION env to build future ppl, cause apparently wrong package versions quietly fail and build successfully while breaking the site. The console erros were fixed by a cache purge. Cheers