# Problems with Force https and mixed https content

**URL:** <https://meta.discourse.org/t/problems-with-force-https-and-mixed-https-content/118337>\
**Category:** Self-hosting\
**Created:** [May 21, 2019, 8:29pm UTC](https://meta.discourse.org/t/problems-with-force-https-and-mixed-https-content/118337 "2019-05-21T20:29:14Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**Post date:** [September 26, 2020, 3:39pm UTC](https://meta.discourse.org/t/problems-with-force-https-and-mixed-https-content/118337/14 "2020-09-26T15:39:27Z")

</div>

My first thought would be to double check your SSO config to see where it is directing users, as well as what origins it accepts. Make sure everything within the SSO config is using `https://`. It’s also possible that this is an Nginx issue. Going to be hard to debug here with multiple variables…

---

_[View the full topic](https://meta.discourse.org/t/problems-with-force-https-and-mixed-https-content/118337)._