A user, biologist, reports that despite enabling HTTPS globally in Discourse and configuring Apache as a reverse proxy with Let’s Encrypt, the login button still appears as HTTP, indicated by an unlocked symbol. simon suggests enabling the force https setting, which the user confirms is already active. RGJ asks for the reverse proxy configuration, hinting at the need for X-Forwarded-Proto. The user provides their Apache config, which includes X-Forwarded-Proto set to HTTPS. Ultimately, biologist confirms the issue is resolved and clarifies that the unlocked symbol does not necessarily mean the connection is insecure.
Yesterday, I’ve been installing Discourse behind an Apache reverse proxy. Apache is mostly managed via a self-service-GUI that can also be used to activate Let’s encrypt-certs and proxy-configuration. Additionaly this GUI takes care, that LE-certs don’t expire. Having said this I want to rule out that I’ve been configuring Discourse without SSL/LE-template; internally I’m using port 10080. Works so far.
However, I discovered there’s an option in Discourse’s config to activate https globally. So I enabled it. This seems to work fine but as I noticed, login-Button is still http (instead auf https). Indeed Discourse indicates this by an unlocked-symbol.
So my question: what do I need to do in order to persuade Discourse to make it https?
Thanks in advance.
If you haven’t done so already, try enabling the Discourse force https site setting. That setting is found in the Security section of your site settings pages.