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. [Bild] darkpixlz: the site works on https fine Except for everything…

[Bild] 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…

[Bild] 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 bein…

DiscourseID kann auf einer Site mit deaktiviertem force-https nicht aktiviert werden

Unterstützung Installation

Falco (Falco) 26. März 2026 um 21:44 4

Sie sollten Ihr Reverse-Proxy-Setup korrigieren und ordnungsgemäßes HTTPS aktivieren.

Thema		Antworten	Aufrufe
Discourse ID fails to activate on my instance SSO unsupported-install , discourse-id	26	675	22. Oktober 2025
Issues with force https, proxy and invitations Support	7	1117	13. Juli 2020
Failed to automatically register with Discourse ID Self-hosting	10	149	27. Mai 2026
Help with setting up Discourse ID Support unsupported-install , discourse-id	28	516	19. November 2025
HTTPS through Proxy; Discourse still trying to get files using HTTP Self-hosting	21	1356	4. April 2020

DiscourseID kann auf einer Site mit deaktiviertem force-https nicht aktiviert werden

Verwandte Themen