Question

Can't access Docker/Portainer Droplet via HTTPS

Posted May 4, 2020 2.4k views
SecurityDocker

I’ve set up a Droplet running Docker (via the one-click install) and installed Portainer on the same droplet via ssh. I’ve also created an A record subdomain.

I managed to access and setup Portainer through the web interface but I can’t access it via https, only http. (despite being able to access my other droplet on same domain via https)

Is there a step I’m missing? (I’m very inexperienced)

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
3 answers

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
edited by MattIPv4

Hello,

Same issue here:

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 0.0.0.0:22              0.0.0.0:*               LISTEN      0          26026      1582/sshd: /usr/sbi 
tcp        0      0 127.0.0.1:35689         0.0.0.0:*               LISTEN      0          65822      17360/containerd    
tcp6       0      0 :::22                   :::*                    LISTEN      0          26037      1582/sshd: /usr/sbi 
tcp6       0      0 :::8000                 :::*                    LISTEN      0          93560      21078/docker-proxy  
tcp6       0      0 :::9000                 :::*                    LISTEN      0          93474      21064/docker-proxy  
udp        0      0 0.0.0.0:53              0.0.0.0:*                           0          62340      16701/unbound       
udp        0      0 0.0.0.0:51820           0.0.0.0:*                           0          62819      -                   
udp        0      0 172.17.0.1:123          0.0.0.0:*                           112        73005      16960/ntpd          
udp        0      0 10.8.0.1:123            0.0.0.0:*                           0          63318      16960/ntpd          
udp        0      0 10.110.0.4:123          0.0.0.0:*                           0          63316      16960/ntpd          
udp        0      0 10.18.0.7:123           0.0.0.0:*                           0          63314      16960/ntpd          
udp        0      0 188.166.38.4:123        0.0.0.0:*                           0          63312      16960/ntpd          
udp        0      0 127.0.0.1:123           0.0.0.0:*                           0          63310      16960/ntpd          
udp        0      0 0.0.0.0:123             0.0.0.0:*                           0          63306      16960/ntpd          
udp6       0      0 :::53                   :::*                                0          62341      16701/unbound       
udp6       0      0 :::51820                :::*                                0          62820      -                   
udp6       0      0 fe80::9885:8aff:fe6:123 :::*                                112        93770      16960/ntpd          
udp6       0      0 fe80::42:73ff:feb5::123 :::*                                112        73012      16960/ntpd          
udp6       0      0 fd42:42:42::1:123       :::*                                0          63328      16960/ntpd          
udp6       0      0 fe80::5049:8fff:fe5:123 :::*                                0          63326      16960/ntpd          
udp6       0      0 fe80::3ccc:62ff:fea:123 :::*                                0          63324      16960/ntpd          
udp6       0      0 2a03:b0c0:2:d0::100:123 :::*                                0          63322      16960/ntpd          
udp6       0      0 ::1:123                 :::*                                0          63320      16960/ntpd          
udp6       0      0 :::123                  :::*                                0          63294      16960/ntpd          
root@VPN:~# 4c860bc980fb^C
root@VPN:~# 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.

and it always show two js files failed to be loaded, please check the screenshot:

https://prnt.sc/10tjmr4

Any suggestion please?