Hello, I tried using Force https and it seemed to work for me except it was causing login problems. However, the logos are loaded using http by default. They should use the // protocol and let the browser decide which one to use, right? Or maybe there is another solution I’m missing? Thanks

Hi Eddie, What version of Discourse are you running? In recent versions logos are uploaded via site settings, instead of being linked using a URL, so this should no longer be an issue.

Hi Joshua, We recently upgraded to v2.2.5. During the previous upgrade, before force https, I believe I deleted the post where the logos were uploaded and switched to the site settings. Everything was fine. Then with v2.2.5, I can’t get rid of the http:// part without force https. I tried reuploadin…

[Bild] EddieOne: Then with v2.2.5, I can’t get rid of the http:// part without force https Sorry, now I’m confused. Is force_https enabled or not? Is there any possibility you’re overriding the uploaded logos via themes? If your force_https is enabled, and your logos are served via site setti…

It was enabled, thought the upgrade was over. Then our QA reports that logins are not working. so we disabled force https for now. You can test here //forum.y8.com I checked the themes and didn’t spot anything that might cause this https problem. We mostly use stock, though it is an old stock theme…

With force_https disabled, I can’t test this. We rely on that setting to ensure assets are served over https, not http. Regarding the login issue, it appears you’re using SSO, so ensure the SSO redirect from your provider links to your site via https://, not http://. Once you’ve re-enabled force_htt…

This forum is using the oauth2 basic plugin. Maybe there is a problem with that, might require a version roll back. Not sure yet. I did check the settings, all addresses were using https, so no obvious problem there.

I have a similar problem here: After finding that the logo and the large icon are loaded via http causing mixed content, enabling force_https fixed this. But login wasn’t possible anymore leading to a redirect loop. After disabling this option, login works again. Why is this happening? And why ar…

What is your login method? I’m guessing it’s not local (username/password) login?

Is there any proxy or other service in front of your installation?

I’m using SSO via another web application. nginx is used as a reverse proxy.

Probleme mit Force HTTPS und gemischtem HTTPS-Inhalt

Unterstützung Installation

EddieOne (Eddie One) 2. Dezember 2020 um 17:10 21

Ich vermute, jemand anderes hat es bereits gesagt, unser DevOps-Team hat es durch einen Patch für Nginx behoben.

proxy_set_header X-Forwarded-Proto $scheme;

Stopper 1: NGINX Proxy Mixed Content Error

Thema		Antworten	Aufrufe
Moved site behind proxy, favicon and header not using https anymore Support	11	2278	26. Mai 2020
Changing force_https does not update the url of uploaded images causing a mixed content warning Bug	7	1504	14. Dezember 2020
Login dialog missing link to logo because DISCOURSE_FORCE_HTTPS set to ‘false’ Support	6	111	9. Dezember 2025
Discourse not aware of SSL termination (mixed content) Self-hosting	9	1911	15. Februar 2023
Mixed SSL since upgrade Self-hosting	14	702	30. Dezember 2022

Probleme mit Force HTTPS und gemischtem HTTPS-Inhalt

Verwandte Themen