I’m consistently encountering mixed-contents errors and need assistance to resolve this. I’m using Nginx (running on AlmaLinux 9.4) to reverse proxy Discourse (standard Docker version 26.1.3, build b72abbb installation) running on Ubuntu 22.04). If I set force https, I cannot log in. The situation …

[image] Problems with Force https and mixed https content Self-hosting I guess someone else already said it, our devops fixed it by patching nginx. proxy_set_header X-Forwarded-Proto $scheme; This thread solves how to force https and get login and all oth…

Stopper 1 solved! No more mixed content messages with any browser (I tried Firefox, Opera and Safari on macOS). This change in Nginx reverse proxy solved also the issue described in my post Problem Responding to a Topic . As a reference, I’m also posting the updated Nginx conf file: server { se…

[image] Ricardo Rodríguez: proxy_set_header X-Forwarded-Proto $scheme; Try hardcoding it to https: proxy_set_header X-Forwarded-Proto https;

[image] Richard - Communiteq: Try hardcoding it to https I was struggling to understand this proposal. Why should we try hardcoding it to https if $scheme works? Thanks!

Stopper 1: NGINX Proxy Mixed Content Error

Support Self-hosting

RGJ (Richard - Communiteq) June 12, 2024, 9:18am 6

I didn’t read very well.

Topic		Replies	Views
Front nginx https reverse proxy to discourse http Self-hosting	2	1644	January 8, 2019
NGINX Proxy Mixed Content Error Self-hosting	1	8909	December 23, 2017
Reverse Proxy Into Discourse Self-hosting	12	759	October 16, 2024
Problems with Force https and mixed https content Self-hosting	20	3917	December 2, 2020
Mixed SSL since upgrade Self-hosting	13	903	December 30, 2022

Stopper 1: NGINX Proxy Mixed Content Error

Related topics