# Sem conexão segura para Discourse auto-hospedado após a última atualização

**URL:** <https://meta.discourse.org/t/no-secure-connection-to-self-hosted-discourse-after-latest-update/376163>\
**Category:** Self-hosting\
**Created:** [Julho 28, 2025, 11:39am UTC](https://meta.discourse.org/t/no-secure-connection-to-self-hosted-discourse-after-latest-update/376163 "2025-07-28T11:39:27Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)\
**Post date:** [Julho 28, 2025, 11:18pm UTC](https://meta.discourse.org/t/no-secure-connection-to-self-hosted-discourse-after-latest-update/376163/8 "2025-07-28T23:18:49Z")

</div>

É este aqui, definitivamente um bug não intencional ao mesclar a configuração ssl-on-boot:

> <https://github.com/discourse/discourse_docker/pull/977>
>
> Allows ssl and letsencrypt templates to run on boot via initscripts
> 
> This chan…ge adds the decision to configure https or letsencrypt to be at runtime
> rather than at build time via env vars.
> 
> Under the hood, these are the commands, just migrated to shellscripts
> that run when a container boots.
> 
> Runs on existence of ENABLE\_SSL (base ssl template)
> or LETSENCRYPT\_ACCOUNT\_EMAIL (ssl template+letsencrypt template)
> 
> Both cases checks and errors on blank hostname.

Atualizei o ENABLE\_SSL para ser 1 por padrão aqui:

> <https://github.com/discourse/discourse_docker/pull/985>
>
> Default ENABLE\_SSL to 1 when template is included.

Obrigado pela observação, @tanya_byrne

---

_[View the full topic](https://meta.discourse.org/t/no-secure-connection-to-self-hosted-discourse-after-latest-update/376163)._
