How do I fix this error displayed in the browser console? Mixed Content: The page at ' ' was loaded over HTTPS, but requested an insecure element ' '. This request was automatically upgraded to HTTPS, For more information see

Something on you site is referring to an asset with http, probably. It might be an image. It might be that a theme component is doing it You should be able to tell in the network section of the developer tools.

Should the force_https setting be on? When I turn this setting on, the site crashes. The problem is in the svg file. The extension of the site logo is svg.

[image] poyrazdursuncan: The problem is in the svg file. The extension of the site logo is svg. So you’ll need to change that to point to https. The force https should be set automatically, but if it’s crashing your site then you may have other issues.

I may be very wrong but that reminds me something. You can try removing your logo, then reuploading it so the full url may be updated. The force https settings has be gone from the interface settings many versions ago though… :face_with_raised_eyebrow: (I’ll remove my message if it is nonsense to avoid misleading people using the search)

[image] Canapin: The force https settings has be gone from the interface settings many versions ago though That’s because the standard install sets it in an environment variable (except for a time last fall when it was broken). Has this site been rebuilt lately? Is it a standard install?

Solved. [image] Install Discourse on a residential internet with Cloudflare Tunnel Sysadmins Since Discourse now has support for running on a Raspberry Pi, running a small instance in your home lab will become a common use case. However, many residential ISPs block incoming traffic to the ports 80/443 that Discourse need. For our demo site at https://discourse-on-a-pi.falco.dev/ we used Cloudflare Tunnel to work around this, and you can do it too! Setup your tunnel First, follow the following guide: The only change you need is changing the URL from url: http://localhost:8000 to url…

Mixed Content: The page at '<URL>' was loaded over HTTPS error

Product Support

poyrazdursuncan (Dursun Can) January 31, 2022, 6:16am 7

Solved.

Topic		Replies	Views
Problems with Force https and mixed https content Self-hosting	20	4036	December 2, 2020
Why is the Apple Touch Icon loaded via HTTP instead of HTTPS? Product Support	28	5199	December 19, 2018
Discourse not aware of SSL termination (mixed content) Self-hosting	7	2074	August 8, 2019
Changing force_https does not update the url of uploaded images causing a mixed content warning Bug	7	1669	December 14, 2020
I am not able to generate my Logo Self-hosting	9	704	April 3, 2024

Mixed Content: The page at '<URL>' was loaded over HTTPS error

Related topics