Hello, on 2 different discourse instances both upgraded to v2.3.0.beta5 +43 the different logo that were previously uploaded in Settings/Required https://{FQDN}/admin/site_settings/category/required are now being served with http:// instead of https:// which now create “Mixed Content” warnings…

ok, so I understand “not a valid bug” because “never was supported” I understand 5/5 what you’re saying here, all good with me

站点徽标与带代理的 HTTPS

codinghorror (Jeff Atwood) 2019 年3 月 16 日 00:37 2

Running https without “force https” set isn’t supported – and never has been.

话题		回复	浏览量
Moved site behind proxy, favicon and header not using https anymore Support	11	2470	2020 年5 月 26 日
Problems with Force https and mixed https content Self-hosting	20	3927	2020 年12 月 2 日
Changing force_https does not update the url of uploaded images causing a mixed content warning Bug	7	1637	2020 年12 月 14 日
Mixed SSL since upgrade Self-hosting	13	903	2022 年12 月 30 日
Discourse not aware of SSL termination (mixed content) Self-hosting	7	2040	2019 年8 月 8 日