Aucune connexion sécurisée à Discourse auto-hébergé après la dernière mise à jour

featheredtoast · Juillet 28, 2025, 11:18

It’s this one here, definitely an unintended bug with merging the ssl-on-boot configuration:

github.com/discourse/discourse_docker

FEATURE: Move letsencrypt scripts to work on boot

main ← runtime-letsencrypt

opened 07:57AM - 16 Jul 25 UTC

featheredtoast

+105 -77

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.

I’ve updated the ENABLE_SSL to be 1 by default here:

Thanks for the catch @tanya_byrne

Sujet		Réponses	Vues
No connection accepted on http / https after fresh installation on Ubuntu 22.04 LTS Installation	5	2252	Décembre 16, 2022
Forum doesn't load after enabling SSL with Let's Encrypt Installation	9	1207	Août 8, 2018
Discourse has stopped opening Installation	39	5745	Mars 19, 2022
CONNECTION REFUSED on self-hosted instance after rebuild Bug	4	74	Juillet 29, 2025
Installed Discourse in Docker, Cannot Connect Installation	6	1835	Août 8, 2021

Aucune connexion sécurisée à Discourse auto-hébergé après la dernière mise à jour

Sujets connexes