Unable to Connect to Portainer UI after Deploying with Docker Swarm on Ubuntu 22.04 LXC Container

[kubilayverboom]

Ask a Question!

Description

I am running Ubuntu 22.04 as an LXC container on Proxmox, and I am encountering issues connecting to Portainer's UI after deploying it with Docker Swarm.

Steps to Reproduce

1. Deploy Portainer CE per documentation
2. Attempt to connect to Portainer UI https://<private_ip>:9443
3. Get the following error ERR_CONNECTION_REFUSED

Expected Behavior
I expect to access the Portainer UI after deployment and be able to manage Docker containers and services via both HTTP and HTTPS.

Actual Behavior
Instead, the UI does not load or responds with connection errors when trying to access both HTTP and HTTPS endpoints.

Additional Information

• Host OS: Ubuntu 22.04 LTS (LXC container on Proxmox)
• Docker Version: 24.0.4
• Portainer Version: 2.19.5
• When deploying Portainer the standard way, I'm able to connect to the UI

[Nick-Portainer]

Can you provide any logs from the running container?

[kubilayverboom]

2024/06/14 01:45PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:369 > encryption key file not present | filename=portainer
2024/06/14 01:45PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:392 > proceeding without encryption key |
2024/06/14 01:45PM INF github.com/portainer/portainer/api/database/boltdb/db.go:125 > loading PortainerDB | filename=portainer.db
2024/06/14 01:45PM INF github.com/portainer/portainer/api/internal/ssl/ssl.go:80 > no cert files found, generating self signed SSL certificates |
2024/06/14 01:45PM INF github.com/portainer/portainer/api/chisel/service.go:193 > Generated a new Chisel private key file | private-key=/data/chisel/private-key.pem
2024/06/14 13:45:05 server: Reverse tunnelling enabled
2024/06/14 13:45:05 server: Fingerprint 7NegMAtee+g1EO+AFZ1Zql2sxHeSviJlSEBM7iu1qD8=
2024/06/14 13:45:05 server: Listening on http://0.0.0.0:8000
2024/06/14 01:45PM WRN github.com/portainer/portainer/api/platform/platform.go:70 > failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
2024/06/14 01:45PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:649 > starting Portainer | build_number=64 go_version=1.21.9 image_tag=linux-amd64-2.19.5 nodejs_version=18.20.2 version=2.19.5 webpack_version=5.88.1 yarn_version=1.22.22
2024/06/14 01:45PM INF github.com/portainer/portainer/api/http/server.go:357 > starting HTTPS server | bind_address=:9443
2024/06/14 01:45PM INF github.com/portainer/portainer/api/http/server.go:341 > starting HTTP server | bind_address=:9000

I saw this issue, so I don't think it's related to my issue:

#8806

[kubilayverboom]

Also also:

* docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-06-14 00:46:24 CEST; 15h ago
TriggeredBy: * docker.socket
       Docs: https://docs.docker.com
   Main PID: 5253 (dockerd)
      Tasks: 12
     Memory: 515.2M
        CPU: 42.721s
     CGroup: /system.slice/docker.service
             `-5253 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Jun 14 15:53:31 tatooine dockerd[5253]: time="2024-06-14T15:53:31.950444382+02:00" level=error msg="Failed to add firewall mark rule in sbox ingress (ingress): open /proc/sys/net/ipv4/vs/conntrack: no such file or directory"
Jun 14 15:53:31 tatooine dockerd[5253]: time="2024-06-14T15:53:31.952121072+02:00" level=error msg="Failed to add firewall mark rule in sbox lb_rr17 (lb-port): open /proc/sys/net/ipv4/vs/conntrack: no such file or directory"
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 01:53PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:519 > instance already has defined environments, skipping the environment defined via CLI |
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 13:53:31 server: Reverse tunnelling enabled
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 13:53:31 server: Fingerprint c3:1b:d5:96:1d:83:8a:3f:ab:f6:ec:39:ce:6f:e3:ff
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 13:53:31 server: Listening on 0.0.0.0:8000...
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 01:53PM WRN github.com/portainer/portainer/api/platform/platform.go:67 > failed to retrieve docker info | error="Cannot connect to the Docker daemon at unix:///var/run/docker>
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 01:53PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:810 > starting Portainer | build_number=27403 go_version=1.19.4 image_tag=linux-amd64-2.17.0 nodejs_versi>
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 01:53PM INF github.com/portainer/portainer/api/http/server.go:342 > starting HTTPS server | bind_address=:9443
Jun 14 15:53:31 tatooine 03c3559c3557[5253]: 2024/06/14 01:53PM INF github.com/portainer/portainer/api/http/server.go:327 > starting HTTP server | bind_address=:9000

[kubilayverboom]

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro

Adding this line to the portainer-agent-stack.yml fixes the issue.

[Nick-Portainer]

Hey, that should of been part of your stack file already when running, see line 6

[kubilayverboom]

I apologize for the confusion. The configuration you show applies to the Portainer agent, not the Portainer application itself. The logs I mentioned earlier are actually from Portainer, not the agent.

[kubilayverboom]

Fortunately, I found a solution! Enabling port forwarding on Docker Swarm within LXC containers was the key. After some searching, I came across this helpful guide:

https://gist.github.com/Drallas/e03eb5a4f68bb526f920a423455bc0c9