For context, I have my Discourse test site running in a Proxmox container behind Nginx (npmplus) on a different server on the same network (but not subnet). Not really anything special. I tried enabling force-https but I kept getting a bunch of CSRF validation errors so I just disabled it again beca…

I’ll come back here for anybody else impacted by this who can’t find a clear answer like I couldn’t: the issue was that I wasn’t using the cloudflare.template.yml file in my app.yml. :sob: After rebuilding with the option enabled it works all good. [image]

The error message Discourse ID returned is complaining that the site’s Redirect URI must be https, so you need to turn on force_https, or otherwise indicate via your proxy configuration the requests are coming in via https. [이미지] darkpixlz: the site works on https fine Except for everything …

[이미지] supermathie: Except for everything that doesn’t: [image] Huh, guess I never noticed any of that. As I said, I tried enabling force_https, but I kept getting CSRF errors doing anything. Maybe the normal nginx variables just don’t work on npmplus (according to the instructions that say …

You should fix your reverse proxy setup and get proper HTTPS working.

I think the issue right now is just weirdness with the variables npmplus is exposing. I had a working config before but I lost it and am not really sure what to do at the moment, I settled on the following but don’t want to enable the setting until I’m 100% sure it’ll work to avoid BAD CSRF and a tr…

[이미지] darkpixlz: it seems to just be rejecting traffic over 443 Cannot dereference this pointer - I believe you are talking about the Discourse container? force_https does not affect whether Discourse serves on port 443 (HTTPS); it only tells Discourse that it should assume it’s always being…

force-https가 비활성화된 사이트에서 DiscourseID를 활성화할 수 없습니다

제품 지원 자체 호스팅

Falco (Falco) 3월 26, 2026, 9:44오후 4

리버스 프록시 설정을 수정하고 올바른 HTTPS를 작동하도록 해야 합니다.

글		댓글	조회수
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	1035	10월 22, 2025
Failed to automatically register with Discourse ID Self-hosting	10	340	5월 27, 2026
Issues with force https, proxy and invitations Product Support	7	1168	7월 13, 2020
Help with setting up Discourse ID Product Support unsupported-install , discourse-id	28	1027	11월 19, 2025
HTTPS through Proxy; Discourse still trying to get files using HTTP Self-hosting	21	1514	4월 4, 2020

force-https가 비활성화된 사이트에서 DiscourseID를 활성화할 수 없습니다

Related topics