# Login-knop onbeveiligd

**URL:** <https://meta.discourse.org/t/login-button-unsecured/177418>\
**Category:** Self-hosting\
**Created:** [27 januari 2021 om 10:07 UTC](https://meta.discourse.org/t/login-button-unsecured/177418 "2021-01-27T10:07:25Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![biologist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/biologist/32/518364_2.png) [@biologist](https://meta.discourse.org/u/biologist)\
**Post date:** [27 januari 2021 om 10:07 UTC](https://meta.discourse.org/t/login-button-unsecured/177418/1 "2021-01-27T10:07:25Z")

</div>

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.

---

_[View the full topic](https://meta.discourse.org/t/login-button-unsecured/177418)._
