Can't get script tag to work in landing pages plugin due to content-security-policy

[TheNab]

inline js script tag isn’t being loaded due to csp and idk how to fix it.

[awesomerobot (Kris)]

There’s some information in this post that may help: Mitigate XSS Attacks with Content Security Policy

@Discourse

CSP and third-party integrations

When using third-party services like Google Tag Manager, Google Analytics, or advertising services, you may need to adjust your CSP settings. In most cases with Discourse version 3.3.0.beta1 or later, external scripts should work without additional configuration due to the ‘strict-dynamic’ CSP implementation.

If you encounter issues, you may need to:

1. Identify the required script sources by monitoring your browser console
2. Add the necessary sources to the content_security_policy_script_src setting
3. For complex integrations like ad services which load external resources, you might need to enable cross-domain rendering (Example PR from discourse-adplugin that does this).

Best practices

1. Start with CSP Report-Only mode to identify potential issues
2. Gradually tighten your CSP as you resolve legitimate violations
3. Regularly review your CSP settings and adjust as needed
4. Be cautious when adding permissive directives like 'unsafe-eval' or 'wasm-unsafe-eval'
5. Keep your Discourse instance updated to benefit from the latest CSP improvements

[TheNab]

I’ve read through that and others but cannot piece together how to actually add the exception to the content_security_policy_script_src

[awesomerobot (Kris)]

Do you see an error concerning the script in your browser console? something like this?

You’ll want to add that provided hash ('sha256-xxxxx') to the “content security policy script src” setting found in admin > all site settings

[TheNab]

The error I was getting had nonce-s0m3h4sh in Firefox browser I wasn’t getting the sha256-s0m3h4sh. But when I just now looked in chrome it was the sha256 one. I suppose that was causing most of my confusion