Cant access dashboard after update to 4.0
Hi,
I have update runtipi to 4.0 but I'm left unable to access the dashboard. I had it setup so I could access the dashboard through a Cloudflare tunnel, but the container hasn't started.
I attempted to access the dashboard using my VPS's IP but I get a timeout, with the firewall (ufw) up or down.
I'm stuck, do you have any pointers?
4 Replies
docker ps:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
db0575930727 traefik:v3.2 "/entrypoint.sh --pr…" 9 minutes ago Up 8 minutes 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp runtipi-reverse-proxy
f28adcc2c19d ghcr.io/runtipi/runtipi:v4.0.3 "docker-entrypoint.s…" 9 minutes ago Up 8 minutes (healthy) 3000/tcp runtipi
372db4c1dc11 postgres:14 "docker-entrypoint.s…" 9 minutes ago Up 9 minutes (healthy) 5432/tcp runtipi-db
313ca35a5839 rabbitmq:4-alpine "docker-entrypoint.s…" 20 minutes ago Up 10 minutes (healthy) 4369/tcp, 5671-5672/tcp, 15691-15692/tcp, 25672/tcp runtipi-queue
I tried to start a separate cloudflared container to see if I could access the Tipi dashboard but I'm also getting an error:
2025-05-24T08:15:01Z ERR Request failed error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:80: connect: connection refused" connIndex=1 dest=https://my.domain/ event=0 ip=xxx.xxx.xxx.xx type=http
2025-05-24T08:15:01Z ERR error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:80: connect: connection refused" connIndex=0 event=1 ingressRule=0 originService=http://localhost:80
I managed to fix it by manually installing the clouflared binary and restoring the original tunnel which allowed me to reach the tipi GUI.
So you were locked out because cloudflare app was not running properly?
correct, I couldn't reach the webui because I had been using the Cloudflared docker image to reach runtipi + my apps, and CF wasn't autolaunched after the migration
Yes okay this is a problem, after 4.0 all apps have to be started manually. I can make this more clear in the docs