john3 encountered a CSP (Content Security Policy) error after upgrading Discourse to “tests-passed” due to mini_racer issues with “stable”. The error blocked loading a script asset, resulting in a blank page. pfaffman noted recent CSP changes and suggested adjusting site settings via the Rails console. pmusaraj confirmed CSP is now enabled by default and provided a workaround: disabling it temporarily by running SiteSetting.content_security_policy = false in the Rails console. john3 confirmed the fix worked but raised two new concerns: the unavailability of a stable release without mini_racer errors, and inability to restore a backup made under the previous stable version while now running tests-passed. The issue highlights migration challenges between Discourse versions and the impact of default CSP enforcement on older or misconfigured instances.
I just upgraded discourse and reinstalled with “tests-passed” as “stable” was giving me mini_racer error. After installation, I am getting a blank page and log shows the following error.
Refused to load https://www.domain.com/community/assets/browser-update-1741a2ed67a367faeb0a582af064457e8b1b1354e52e6efcf8bf26301166dec8.js because it does not appear in the script-src directive of the Content Security Policy.
However, I don’t think if I have enabled CSP in the server configuration.
yes its working now. Thank you. When will stable release be available? I mean currently its giving me mini racer error.
Update: Now I am unable to restore the previous backup which I made on stable release, but this time as stable is giving error so I am using tests-passed.