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 …

[изображение] 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 a…

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…

[изображение] Ricardo Rodríguez: proxy_set_header X-Forwarded-Proto $scheme; Try hardcoding it to https: proxy_set_header X-Forwarded-Proto https;

[изображение] 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!

Шаг 1: ошибка смешанного контента в прокси NGINX

Поддержка Самостоятельное хостинг

rrodrigueznt (Ricardo Rodríguez) 12.Июнь.2024 08:55:27 5

Мне было трудно понять это предложение. Зачем мы должны пытаться прописать https вручную, если работает $scheme? Спасибо!

Тема		Ответов	Просм.
Front nginx https reverse proxy to discourse http Self-hosting	3	1586	23.01.2019
NGINX Proxy Mixed Content Error Self-hosting	2	8873	24.12.2017
Reverse Proxy Into Discourse Self-hosting	12	563	16.10.2024
Problems with Force https and mixed https content Self-hosting	20	3660	02.12.2020
Mixed SSL since upgrade Self-hosting	14	748	30.12.2022

Шаг 1: ошибка смешанного контента в прокси NGINX

Связанные темы