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

Site-Logos und HTTPS mit Proxy

codinghorror (Jeff Atwood) 16. März 2019 um 00:37 2

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

Thema		Antworten	Aufrufe
Moved site behind proxy, favicon and header not using https anymore Support	11	2470	26. Mai 2020
Problems with Force https and mixed https content Self-hosting	20	3926	2. Dezember 2020
Changing force_https does not update the url of uploaded images causing a mixed content warning Bug	7	1637	14. Dezember 2020
Mixed SSL since upgrade Self-hosting	13	903	30. Dezember 2022
Discourse not aware of SSL termination (mixed content) Self-hosting	7	2040	8. August 2019