# Nginx as reverse proxy and Content Security Policy issue

**URL:** <https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288>\
**Category:** Self-hosting\
**Tags:** nginx\
**Created:** [August 19, 2024, 3:55pm UTC](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288 "2024-08-19T15:55:18Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![sandra.mccollum](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sandra.mccollum/32/441742_2.png) [@sandra.mccollum](https://meta.discourse.org/u/sandra.mccollum)\
**Post date:** [August 19, 2024, 5:04pm UTC](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288/5 "2024-08-19T17:04:19Z")

</div>

Yea, did that, same problem.

As a test I even added unsafe-inline, still same problem with login rendering and group avatars.

If I comment out the policy, it all works as expected..

---

_[View the full topic](https://meta.discourse.org/t/nginx-as-reverse-proxy-and-content-security-policy-issue/322288)._