# 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:** 18

<div class="post-metadata">

**Author:** ![v.stephan](https://avatars.discourse-cdn.com/v4/letter/v/85f322/32.png) [@v.stephan](https://meta.discourse.org/u/v.stephan)\
**Post date:** [November 30, 2020, 4:58pm UTC](https://meta.discourse.org/t/problems-with-force-https-and-mixed-https-content/118337/18 "2020-11-30T16:58:14Z")

</div>

Hey there,

sorry to bring this up again. But in fact I am not getting rid of my mixed content warnings in firefox. The funny thing is, I have quite the same setup … more or less. Maybe someone can bring in some ideas or improvements. Wenn I am not that kind of a big expert in Apache directives. But it makes sense for me – a bit at least.

We have discourse in docker on Apache through RevereseProxy and handle the Lets Encrypt certs with ISP Config as we have a lot of “normal” domains running on our server.

We set up the Reverse Proxy with Apache directives by ISP Config. Our Setup looks like this:

```plaintext
ProxyPreserveHost On
ProxyPass /.well-known/acme-challenge !
RequestHeader set X-Forwarded-Proto "https"
ProxyPass / unix:///var/discourse/shared/standalone/nginx.http.sock|http://localhost/
ProxyPassReverse / unix:///var/discourse/shared/standalone/nginx.http.sock|http://localhost/

RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteRule (.*) https://sub.domain.de$1 [R,L]

```

We still have mixed content warings in firefox. What I tried is to set `force ssl option` in settings. As a first effect we could not log in anymore. We just authenticate by user and pw. So I tried the fixe mentioned

> [@alphanoob1337](#):
>
> `RequestHeader set X-Forwarded-Proto "https"`

Well, `force ssl` and login is possible now. But we still have firefox showing mixed content warnings. Console says:

> [http://forum.suro2030.de/uploads/default/optimized/2X/6/67817e7f1257a3f393ecc85c43dd9bdcce217fca\_2\_180x180.png](http://forum.suro2030.de/uploads/default/optimized/2X/6/67817e7f1257a3f393ecc85c43dd9bdcce217fca_2_180x180.png)

and

> [http://forum.suro2030.de/uploads/default/optimized/2X/4/4f5d4076a6a0e6641183b611d49a72f639ca69f8\_2\_32x32.png](http://forum.suro2030.de/uploads/default/optimized/2X/4/4f5d4076a6a0e6641183b611d49a72f639ca69f8_2_32x32.png)

are delivered by http … We also tried to repuload those branding images using `sub.domain.de/wizard` but we still are running in this issues … is there a way to … I do not know force to re-render the optimized images using https? Is something wrong with our Reverse Proxy setup?

I would so thankful on further assistance here. It is like a ocean of possible Reverse Proxy configurations with forcing ssl by Lets Encrypt (handled by) Apache (and not not build in discourse config) so I think I drowning. And I have the feeling that there are just a few people using Apache as a host with Reverse Proxy and that Lets Encrypt setup we are using. Or we are just the ones configuring it wrong.

Well as I said, I would appreciate any hints. Thanks in advance!

---

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