A user, tanya_byrne, reports a CONNECTION REFUSED error on a self-hosted Discourse instance after a rebuild, despite no changes to configuration or SSL certificates. The issue appears linked to a recent PR (#977) that modified the web.ssl.template.yml file, causing SSL setup failures. tanya_byrne identifies that the ENABLE_SSL variable must now be set in app.yml for the template to function correctly. After adding this variable, the connection issue was resolved. featheredtoast confirms a fix is incoming via PR #985, and notes the documentation should be updated to reflect this change.
As mentioned in this thread, No secure Connection to self-hosted Discourse after latest update - Support - Discourse Meta there appears to be an issue on rebuild causing aCONNECTION REFUSED issue.
No changes in configuration or SSL cert have been made to this instance and the cert was working fine before the most recent rebuilds.
Info from my logs found here: No secure Connection to self-hosted Discourse after latest update - #5 by tanya_byrne
I believe that this PR has introduced the issue FEATURE: Move letsencrypt scripts to work on boot by featheredtoast · Pull Request #977 · discourse/discourse_docker · GitHub specifically with the change to `templates/web.ssl.template.yml`. I reverted this file back to how it was before this change, and now my forum loads with no issue
It looks as ENABLE_SSL is checked and should exist in the app.yml file now. That would explain why this was failing. Base template docs / and repo should be updated in this case to document this new var. Have added this var to my app.yml and am using the most recent templates/web.ssl.template.yml and connection is no longer refused.
Pardon the dust - as mentioned in the other topic, fix is incoming here:
This topic was automatically closed after 19 hours. New replies are no longer allowed.