My Discourse instance is behind a proxy: server { server_name forum.[...]; location / { proxy_pass http://IP_ADDRESS; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; p…

If you’re proxying, this can go wrong. In my experience this is the #1 reason for the issues you are describing. Try to set it to “https” instead (maybe just skip the variable, just put “https” there).

It looks like I’m really missing something. Being unable to force HTTPS implies that the logo cannot be displayed (not so serious for the time being). I’ve just discovered today I also get a CSRF-related error (“forbidden”) when I try to remove a task in Sidekiq. This is what I found in /var/discour…

Maybe you just need to the froce https enable on your front proxy, and disable on discourse.

@hawm I think this is my current configuration.

[изображение] Felip: proxy_set_header X-Forwarded-Proto $scheme; How are you setting the $scheme variable?

[изображение] michaeld: How are you setting the $scheme variable? I don’t, I guess I rely on the default value , is this wrong?

@michaeld yes! You nailed it! Thank you so much!

Проблемы с принудительным HTTPS, прокси и приглашениями

Поддержка

michaeld (Michael - Communiteq) 12.Июль.2020 08:38:06 5

Как вы устанавливаете переменную $scheme?

Тема		Ответов	Просм.
Moved site behind proxy, favicon and header not using https anymore Support	11	2293	26.05.2020
403 Error when changing any settings after enabling force_https with proxy Support	5	986	30.11.2019
Can't enable DiscourseID on a site with force-https disabled Self-hosting discourse-id	6	92	20.04.2026
SSL problem with SSL proxy Self-hosting	6	743	13.07.2022
DiscourseConnect generates HTTP redirects even with force_https on Self-hosting discourseconnect	4	332	27.05.2024

Проблемы с принудительным HTTPS, прокси и приглашениями

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