Hi @christiaanb,

It sounds like you don’t have anything listening on port 443(https). To check that, please SSH to your droplet

ssh root@YourDropletIP

And run the following command

netstat -tulpen

If you have 443 there than your droplet is listening on the said port for https.

Alternatively, the port in question might be 8443. This again can be checked with the netstat command I posted above.

Additionally, if you execute

docker service logs portainer

OR

docker logs <portainer_container>.

What do you see?

Regards,
KDSYs

Thanks @KDSys. I’m accessing via port 9000 because that’s what the install docs said: “You’ll just need to access the port 9000 of the Docker engine where portainer is running using your browser.”

Here’s what I’m seeing:

netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      101        630819     3446/systemd-resolv 
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          22240      1137/sshd           
tcp6       0      0 :::22                   :::*                    LISTEN      0          22251      1137/sshd           
tcp6       0      0 :::9000                 :::*                    LISTEN      0          963693     19968/docker-proxy  
udp        0      0 127.0.0.53:53           0.0.0.0:*                           101        630818     3446/systemd-resolv 

docker service logs portainer
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.

docker logs <portainer_container>.
-bash: portainer_container: No such file or directory