The user nekodroid is troubleshooting issues while setting up HTTPS with Let’s Encrypt for their Discourse instance. Initially, they encountered a 443: bind: address already in use error during app rebuild, which was traced to a misconfigured app.yml and a potential Docker installation issue. After restarting the installation, they faced DNS and port accessibility problems, with the server showing an Nginx welcome page instead of the Discourse installation interface. The community suggests checking DNS records (specifically an A record), clearing browser cache, and ensuring the installation process is completed. The user also reports difficulties with the registration step, and another user, darkjstrolm, confirms a similar issue with Let’s Encrypt on DigitalOcean. The discussion highlights common pitfalls in self-hosted Discourse setups, including DNS configuration, port forwarding, and Let’s Encrypt integration nekodroid, pfaffman, ufukayyildiz, darkjstrolm.
So I was trying to enable HTTPS for my website following this nice tutorial. Everything went fine until I tried rebuilding the app, typing ./launcher rebuild app.
I ran discourse-doctor to try figuring this out and I finally found something :
==================== END REBUILD LOG ====================
Failed to rebuild app.
Checking your domain name . . .
Connection to discourse.mydomain.com succeeded.
You should probably remove any non-standard plugins and rebuild.
Attempting to restart existing container. . .
starting up existing container
+ /usr/bin/docker start app
Error response from daemon: driver failed programming external connectivity on endpoint app (some_random_characters): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use
Error: failed to start containers: app
Failed to restart the container.
Note : I’ve replaced a long chain of characters with some_random_characters and my domain name with discourse.mydomain.com.
This pretty weird since I sticked up to the tutorial ; I have no idea of how to fix this.
I had actually read this guide, and it blocked on the command wget -qO- https://get.docker.com/ | sh ; it said “wrong usage of command wget” from what I remember. So I skipped to the next steps, and I remember Docker being auto-installed after typing the command ./discourse-setup.
This is probably my problem…
I will completely restart my Discourse installation from the beginning then update this thread.
I’ve ran the discourse-setup autosetup program and added an email adress for Let’s encrypt encryption when prompted. Now it says that :
Checking your domain name . . .
WARNING:: This server does not appear to be accessible at discourse.apertureproject.me:443.
A connection to http://discourse.apertureproject.me (port 80) also fails.
According to this, the error is due to unopened ports, and I absolutely got no idea of how to fix this. And I wouldn’t launch my website without encryption, so I won’t disable Let’s Encrypt.
EDIT !
I’ve found my host’s documentation (OVH) about how to open ports. But my IP manager is empty, and it should be filled with several IP adresses according to the doc’s screenshots.
I’m sorry, it’s in french, but as you can see, the IP adresses list is completely empty.