I’ve since moved my Discourse instance between servers, and is now running behind a reverse proxy with SSL termination. However, the header image and favicon are not being requested over HTTPS and getting blocked. I tried setting “force https” to on, but this hasn’t helped. [image]

Is your proxy supplying an X-Forwarded-Proto header? (It should).

Is your proxy supplying an X-Forwarded-Proto header? (It should). Yes it is.

I had the same issue. I have a Discourse instance behind HAProxy with SSL termination. The fix is pretty simple, but not obvious: First make sure that “force https” is enabled in the settings (go to Settings and filter by “force https”). Go to Settings > Branding > and just re-upload your logos. E…

Hello, I’d like to come back along this issue. Actually, I’ve the same problem, and I can’t use force_https to true since there is no way to login… (Unknown error at the login). How can we force the logo to be referenced with a https request and not http? Shouldn’t it be easy? So many thanks for…

You’ll need to flip the force_https site setting via SSH-ing into the server and entering the Ruby command line. There are howto topics on doing that here.

Thanks for your reply. I was certainly unclear in my message. Actually, I can manage to change force_https using rails command, no problem. So, just to be clearer: Until the last upgrade I’ve performed a couple of days ago which needed to rebuild the docker container, I had a full running solution …

In addition, I also found the following site setting which has the guilty URL: SiteSetting.site_favicon_url (another is SiteSetting.site_apple_touch_icon) with the “http://…jpeg”. However, it seems not obvious to change the value with a simple rail command as we do with force_https for example)…

Please, any help about this topic?

You set those via the setup wizard. Re-run the setup wizard and re-upload the images.

I set the images like that. I re-launched the wizard, but with the same effect at the end :frowning: I guess uploading the pictures does not impact on the way how they are referred; it is more a thing related to the web page generation.

将站点移至代理后，favicon 和 header 不再使用 https

支持

rossierd (Daniel Rossier) 2020 年5 月 22 日 08:28 11

我就是这样设置图片的。我重新启动了向导，但结果还是一样：
我觉得上传图片不会影响它们的引用方式；这更多是与网页生成相关的问题。

Facebook Login Error: CSRF detected

话题		回复	浏览量
Problems with Force https and mixed https content Self-hosting	20	3614	2020 年12 月 2 日
Site logos and https with proxy Self-hosting	3	1109	2022 年5 月 5 日
Changing force_https does not update the url of uploaded images causing a mixed content warning Bug	7	1504	2020 年12 月 14 日
403 Error when changing any settings after enabling force_https with proxy Support	5	983	2019 年11 月 30 日
Login-button unsecured Self-hosting	5	546	2021 年2 月 2 日

将站点移至代理后，favicon 和 header 不再使用 https

相关话题