I have Discourse installed in a Ubuntu 18.04 VPS following the standard install instructions. It’s been running well for a couple of years now, but when I went to my site this afternoon, the TLS cert was expired–and since it uses HSTS, that means I was completely locked out of the site. Easy enough, I thought, SSH into the server, install updates (just because), run
./launcher rebuild app, and she’ll be right, mate.
Nope, it didn’t work that way; I got an “oops” page. So I decided to reboot the system, and now I’m getting a 502 page when I try to browse there. I can’t start
root@talk:/var/discourse# ./launcher start app x86_64 arch detected. starting up existing container + /usr/bin/docker start app Error response from daemon: driver failed programming external connectivity on endpoint app (e5db356e19c947c3e1e20a337aea7ee4bdcfa9bc5f3eac485e76439f3ed3a0e9): Bind for 0.0.0.0:443 failed: port is already allocated Error: failed to start containers: app
…and there is indeed something listening on port 443:
root@talk:/var/discourse# netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 906/docker-proxy tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 427/systemd-resolve tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 918/docker-proxy tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 892/docker-proxy tcp6 0 0 :::9936 :::* LISTEN 578/sshd udp 0 0 127.0.0.53:53 0.0.0.0:* 427/systemd-resolve
I’m afraid I’m stumped–what should I check next?