portainer: Connection refused
Hi, my server has been running portainer for 2+ years, this morning it ran into a / partition with an extremely large (55GB) docker volume for portainer.
I stopped dockerd, deleted portainer and redeployed it straight from https://www.portainer.io/installation/
docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
I’ve also tried docker run -d -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer which was my legacy command.
I even deleted and recreated my own portainer_data folder.
I am always getting a connection refused (ERR_CONNECTION_REFUSED) message in my browser.
I tried to deploy a basic nginx image listening on port 9000 and it worked, so I know this is not a firewall issue.
I have other containers running that listen on ports 22, 80, 443, 5432, and they are all reacheable.
I’ve upgraded docker to the latest version, I’ve tried to launch portainer with the --privileged flag, but no luck.
I also found a reply suggesting to use portainer/portainer:develop but it threw docker: Error response from daemon: manifest for portainer/portainer:develop not found: manifest unknown: manifest unknown.
I’ve been struggling for hours, reading all issues with the words “timeout” and “refused”, I’m stuck.
Any idea?
OS
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
logs
root@gitlab:/# docker logs portainer
2020/08/10 09:56:27 Templates already registered inside the database. Skipping template import.
2020/08/10 09:56:27 Starting Portainer 1.19.1 on :9000
netstat
root@gitlab:/# netstat -tulpan | grep LISTEN
tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN 1209/sshd
tcp 0 0 10.0.3.1:53 0.0.0.0:* LISTEN 1120/dnsmasq
tcp6 0 0 :::9000 :::* LISTEN 3711/docker-proxy
tcp6 0 0 :::2222 :::* LISTEN 1209/sshd
tcp6 0 0 :::80 :::* LISTEN 21915/docker-proxy
tcp6 0 0 :::22 :::* LISTEN 21944/docker-proxy
tcp6 0 0 :::5432 :::* LISTEN 21886/docker-proxy
tcp6 0 0 :::443 :::* LISTEN 21900/docker-proxy
docker info
Client:
Debug Mode: false
Server:
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 7
Server Version: 19.03.12
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
init version: fec3683
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-142-generic
Operating System: Ubuntu 16.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.792GiB
Name: gitlab
ID: RNUT:QKVD:5DMM:F6XQ:MJWW:QIAU:3JTK:NTNS:YHH7:INAE:42VO:KWWG
Docker Root Dir: /storage1/docker
Debug Mode: false
Username: italic
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 22
hi everyone! i found this topic trying to fix my “connection refused” after install portainer. i fixed issue using https.