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 all other…

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) 6월 12, 2024, 8:55오전 5

이 제안이 이해가 잘 안 되었습니다. $scheme가 작동하는데 왜 굳이 https로 하드코딩해야 하는 건가요? 감사합니다!

글		댓글	조회수
Front nginx https reverse proxy to discourse http Self-hosting	2	1644	1월 8, 2019
NGINX Proxy Mixed Content Error Self-hosting	1	8909	12월 23, 2017
Reverse Proxy Into Discourse Self-hosting	12	759	10월 16, 2024
Problems with Force https and mixed https content Self-hosting	20	3924	12월 2, 2020
Mixed SSL since upgrade Self-hosting	13	903	12월 30, 2022

1단계: NGINX 프록시 혼합 콘텐츠 오류

Related topics