It seems that my containers running on the docker have problems listening to the 443 port. root@vultr:/var/discourse# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ed694ee6041b local_discourse/app "/sbin/boot" 14 minutes ago Created app 2c0e953c6a3f discourse/base:2.0.20181031 "/bin/bash -c 'cd ..." 8 hours ago Exited (143) 8 hours ago unruffled_clarke While it should be root@vultr:/var/discourse# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b6c9cde8ee4a local_discourse/app "/sbin/boot" 12 days ago Up 4 days 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app I tried to change the domain of the discourse site but seems the web condition is not so good, that caused there being an “app.yml.swap” file and the ssh connectivity stopped. Then I found a new place with better web condition and tried rebuilding the app discourse.The rebuilding process ends well but it seems that something is already running and occupied the 443 port /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint app (56426f5559c3daa85c652e960468e83ab887ca4a79376a857da359604a1d233f): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use.

I think its the letsencrypt of the former website‘'s fault. I simply deleted the old letsencrypt folder “AAAA.com”, now there only being a folder of “BBBB.com”. And now the website works fine. [image]

Where is this hosted? Is there another webserver already on the machine?

NO. There’s only one docker and only one discourse running on the server. I only want to change the discourse name form AAAA.com to BBBB.com （don’t click, only for example）

Well something is listening on 443, and as you’ve evidenced in your list it’s not docker.

If there’s a website on the machine in addition to a discourse install you can’t free up 443 just by renaming the site. Your server can only have one application listening under that port. If you netstat -tulpn | grep 443 what’s the output?

docker ps What is the output of that?

Docker engine with 443 port already occupied

Product Support

xiasummer (xiasummer) February 11, 2019, 2:58pm 7

Now it woks fine

tcp6       0      0 :::443                  :::*                    LISTEN      5677/docker-proxy

Topic		Replies	Views
Error response on port 443 Product Support	3	1646	June 11, 2017
Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use Self-hosting	3	7220	March 15, 2021
443 address already in use? Letencrypt Self-hosting	5	3472	January 3, 2018
Bind for 0.0.0.0:443 failed: port is already allocated Self-hosting	1	4837	May 19, 2020
Site's down - app won't start, port 443 conflict? Self-hosting	4	839	March 15, 2022

Docker engine with 443 port already occupied

Related topics