A user reports blocked mixed content errors for fonts in the browser console, despite the site using HTTPS. The issue occurs with fonts selected via the Discourse Wizard, with URLs referencing http:// instead of https://. griffin suggests using the upgrade-insecure-requests Content-Security-Policy header as a temporary fix, which the user confirms works. griffin explains the issue likely stems from incorrect url() references in CSS @font-face rules. The user notes the problem persists in standard Discourse installations, possibly limited to desktop view, and shares the issue privately with the Discourse Team. 4ong acknowledges the root cause remains unclear but accepts the workaround.
I see next errors in browser console.
But I can’t find how to fix that - everything works fine, https:// from the beginning. I’ve tried to relaunch wizard to use different fonts - but it doesn’t help.
Any ideas how can I try to fix this? Thanks!
Do the URLs of the mentioned resources inside the page actually begin with “https”? Any resource loaded with an “http” URL will be considered mixed content.
One hack/bandaid you can use is to include the following header in the offending page:
It’s likely that some of the URLs for loading your font packages have “http” in them. This frequently happens with CSS @font-face rules when using url sources and with the Google Fonts API.