A Content Security Policy (CSP) serves as an extra layer of security implemented by some websites. It grants developers enhanced control over the types of resources allowed to load on your website. To ensure the seamless functioning of Hushly, you must update your Content Security Policy (CSP).
How to spot a CSP issue
You can spot a CSP issue if you see unexpected changes on your site. For example, you may see an image that didn't load correctly, or some CSS that looks slightly off.
To verify if CSP is causing the issues:
- Right-click on a page, click Inspect
- Click Console at the top of the developer window.
- If there are CSP errors, you are likely to encounter a message similar to the following:
Setting up your CSP for Hushly
To solve the errors, you'll need to allow-list the following domains on your content security policy:
connect-src: *.hushly.comimg-src: *.hushly.comscript-src: *.hushly.comframe-ancestors: https://app.hushly.com
Additionally, if you want to use Hushly's custom javascript feature, add unsafe-inline to your script-src directive.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article