# SSL מעורב מאז השדרוג

**URL:** <https://meta.discourse.org/t/mixed-ssl-since-upgrade/250193>\
**Category:** Self-hosting\
**Created:** [30 בדצמבר,‏ 2022,‏ 12:17pm UTC](https://meta.discourse.org/t/mixed-ssl-since-upgrade/250193 "2022-12-30T12:17:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [30 בדצמבר,‏ 2022,‏ 12:36pm UTC](https://meta.discourse.org/t/mixed-ssl-since-upgrade/250193/3 "2022-12-30T12:36:56Z")

</div>

Hi Andrew - thanks for the report. This issue specifically affects reverse-proxy configurations where multiple `X-Forwarded-Proto` headers are added to the request before it hits the application container.

I’ve just merged a fix into `main` - it should hit tests-passed in about 20 minutes

[https://github.com/discourse/discourse/commit/584a6e35528800dffa23c2fb5525000dde8fa931](https://github.com/discourse/discourse/commit/584a6e35528800dffa23c2fb5525000dde8fa931)

Once it appears in [tests-passed](https://github.com/discourse/discourse/commits/tests-passed) you’ll need to do a full rebuild (nginx config changes are not applied during UI-based upgrades).

---

_[View the full topic](https://meta.discourse.org/t/mixed-ssl-since-upgrade/250193)._