I would to redirect users that access the discourse site on port http to port https. I have checked force https but that does not seem to be causing a redirect to happen. The SSL termination is being done external to discourse (discourse always listens on 80).

[Bild] arothberg: The SSL termination is being done external to discourse (discourse always listens on 80) So add a HSTS header there.

What does the force https setting do if it doesnt set HSTS and it doesnt do a 3xx redirect?

[Bild] arothberg: What does the force https setting do if it doesnt set HSTS and it doesnt do a 3xx redirect? Add the SSL-only cookies among other things . In our recommended way to setting SSL, this is all handled automatically: templates/web.ssl.template.yml master …

That template seeks to handle the SSL termination entirely. Would be nice to have a simpler template for cases where termination is handled by eg the load balancer. Also ,I think that even with that flag set, I a seeing cookies with out the secure flag set.

Hey @Falco , let me get into this conversation… I’ve the same proble as @arothberg described. I am using a AWS Load Balancer with an Amazon Issued Certificate. When i was accessing my forum by https://www.forum.com.br it worked fine, but when accessing by forum.com.br , as the default is http, not w…

I’ve replace the entire web.ssl.template.yml with both snippets as i said above.

Did you solved that problem ? geting same bug …

For people who use AWS Classic Load Balancer still trying to solve this. You should read this page: Use Elastic Load Balancing to redirect HTTP traffic to HTTPS | AWS re:Post Basically, Ngnix should redirect to https if X-Forwarded-Proto: http . This header is set by the load balancer. Thus the co…

Great hint indeed ! Thanks :pray: I can confirm that using the X-Forwarded-Proto to redirect the requests also works like a charm with Google Cloud’s HTTPS Load Balancer, if anyone wonders :wink:

Force Redirect HTTP to HTTPS

Product Support

MrBuBBLs (Philippe Boblet) 12. Februar 2021 um 13:26 10

Wirklich ein toller Hinweis! Danke

Ich kann bestätigen, dass die Umleitung der Anfragen über X-Forwarded-Proto auch mit dem HTTPS-Load-Balancer von Google Cloud hervorragend funktioniert, falls sich jemand fragt

Thema		Antworten	Aufrufe
How do I configure Discourse behind an AWS or Google Cloud Proxy with SSL Self-hosting	20	3606	25. März 2019
Website does not forward to https Self-hosting	11	1007	12. März 2020
DiscourseConnect generates HTTP redirects even with force_https on Self-hosting discourseconnect	4	402	27. Mai 2024
X-Forwarded-For proxy tag not recognized by Discourse? Self-hosting	9	3148	19. Januar 2018
Installing discourse with http only (no https) Self-hosting	1	1448	9. Mai 2021

Force Redirect HTTP to HTTPS

Verwandte Themen