Portainer was previously running (some weeks back), no issues and I often leave this time period in-between checking / using Portainer and my containers.
Now when requesting http://server:9000
it just says “Loading Portainer” with some animation. Nothing happens.
So I stopped & removed the container, pulled the latest (1.24.1) image and redeployed with syntax (taken from the Portainer installation web page and having created a Docker volume):
sudo docker run -d -p 9000:9000 --name=portainer -v portainer_data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
This still didn’t work. So I added the extra 8000 port, which I haven’t had to do previously:
sudo docker run -d -p 9000:9000 -p 8000:8000 --name=portainer -v portainer_data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
But I have another web server running on this port number. So I tried adjusting this:
sudo docker run -d -p 9000:9000 -p 8001:8000 --name=portainer -v portainer_data:/data -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
Same result. Viewing the log files:
$ sudo docker logs -f portainer
2020/08/19 11:54:21 Warning: the --template-file flag is deprecated and will likely be removed in a future version of Portainer.
2020/08/19 11:54:22 Templates already registered inside the database. Skipping template import.
2020/08/19 11:54:22 server: Reverse tunnelling enabled
2020/08/19 11:54:22 server: Fingerprint 15:1c:62:50:96:2e:d2:c3:e6:4b:40:59:f8:4f:80:a4
2020/08/19 11:54:22 server: Listening on 0.0.0.0:8000...
2020/08/19 11:54:22 Starting Portainer 1.24.1 on :9000
2020/08/19 11:54:22 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]
If I check the listening port (8001):
$ netstat -ano | grep 8001
tcp6 0 0 :::8001 :::* LISTEN off (0.00/0/0)
Its listening on IPv6!!!
And now we are caught up with the history… Can anyone assist please?