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.