R
Runtipiβ€’3mo ago
frankynov

No more Tipi web interface after latest 4.2.0 update and custom port

Hello everyone, I have performed the latest update from 4.1.x to 4.2.0 on my Debian 12 ARM server on Hetzner. It looks like I can't reach the tipi web ui anymore sadly. My environment is made in the state config file so that it should listen to port 8080 but it's not reachable. Here is the output of the mandatory CLI debug in attachment. Note : docker logs runtipi-reverse-proxy doesn't return anything. The app.log gives this :
2025-06-02T21:33:24.819Z - info > Logs flushed
2025-06-02T21:33:24.829Z - info > Running version: v4.2.0
2025-06-02T21:33:24.830Z - info > Generating system env file...
2025-06-02T21:33:26.414Z - error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.3:5672 Error: connect ECONNREFUSED 172.18.0.3:5672
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
2025-06-02T21:33:26.431Z - warn > RabbitMQ connection lost, attempting to reconnect...
2025-06-02T21:33:29.121Z - info > Creating traefik folders
2025-06-02T21:33:29.124Z - info > Copying traefik files
2025-06-02T21:33:29.128Z - info > Creating base folders
2025-06-02T21:33:29.134Z - info > Creating media folders
2025-06-02T21:33:29.179Z - info > Connected to the queue
2025-06-02T21:33:29.211Z - info > TLS certificate for tipi.local already exists
2025-06-02T21:33:30.482Z - info > Connected to the queue
2025-06-02T21:33:32.058Z - info > Connected to the queue
2025-06-02T21:33:24.819Z - info > Logs flushed
2025-06-02T21:33:24.829Z - info > Running version: v4.2.0
2025-06-02T21:33:24.830Z - info > Generating system env file...
2025-06-02T21:33:26.414Z - error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.3:5672 Error: connect ECONNREFUSED 172.18.0.3:5672
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
2025-06-02T21:33:26.431Z - warn > RabbitMQ connection lost, attempting to reconnect...
2025-06-02T21:33:29.121Z - info > Creating traefik folders
2025-06-02T21:33:29.124Z - info > Copying traefik files
2025-06-02T21:33:29.128Z - info > Creating base folders
2025-06-02T21:33:29.134Z - info > Creating media folders
2025-06-02T21:33:29.179Z - info > Connected to the queue
2025-06-02T21:33:29.211Z - info > TLS certificate for tipi.local already exists
2025-06-02T21:33:30.482Z - info > Connected to the queue
2025-06-02T21:33:32.058Z - info > Connected to the queue
and the error.log :
2025-06-02T21:33:26.414Z - error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.3:5672 Error: connect ECONNREFUSED 172.18.0.3:5672
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
2025-06-02T21:33:26.414Z - error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.3:5672 Error: connect ECONNREFUSED 172.18.0.3:5672
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1636:16)
` The apps hosted by Tipi seem to run fine but I have no access to the management dashboard. Any idea ? Thank you ! πŸ™‚
12 Replies
Nyarlathotep
Nyarlathotepβ€’3mo ago
I had a similar experience. I stopped runtipi via runtipi-cli and started it again. First I tried restart, but that didn't work. After explicitly stopping and starting, it worked fine again.
frankynov
frankynovOPβ€’3mo ago
Ah, I got some more progress, more errors after a stop and trying to start Tipi, here is the output :
root@hetzner-arm:~/runtipi# ./runtipi-cli stop
βœ“ Runtipi successfully stopped
root@hetzner-arm:~/runtipi# ./runtipi-cli start
βœ“ User permissions are ok
βœ“ Copied system files
βœ“ Generated .env file
βœ“ File permissions ok
βœ“ Images pulled
βœ“ Existing containers stopped
βœ— Failed to start containers

Debug: Container runtipi-queue Creating
Container runtipi-db Creating
Container runtipi-queue Created
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-db Starting
Container runtipi-queue Starting
Container runtipi-db Started
Container runtipi-queue Started
Container runtipi-db Waiting
Container runtipi-db Healthy
Container runtipi Starting
Container runtipi Started
Container runtipi Waiting
Container runtipi Healthy
Container runtipi-reverse-proxy Starting
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint runtipi-reverse-proxy (33a1ae9f4fc94f5e3ec91d6989e5ce2ccb048703f172f9765b1e54926b97e96a): Bind for 0.0.0.0:80 failed: port is already allocated
root@hetzner-arm:~/runtipi# ./runtipi-cli stop
βœ“ Runtipi successfully stopped
root@hetzner-arm:~/runtipi# ./runtipi-cli start
βœ“ User permissions are ok
βœ“ Copied system files
βœ“ Generated .env file
βœ“ File permissions ok
βœ“ Images pulled
βœ“ Existing containers stopped
βœ— Failed to start containers

Debug: Container runtipi-queue Creating
Container runtipi-db Creating
Container runtipi-queue Created
Container runtipi-db Created
Container runtipi Creating
Container runtipi Created
Container runtipi-reverse-proxy Creating
Container runtipi-reverse-proxy Created
Container runtipi-db Starting
Container runtipi-queue Starting
Container runtipi-db Started
Container runtipi-queue Started
Container runtipi-db Waiting
Container runtipi-db Healthy
Container runtipi Starting
Container runtipi Started
Container runtipi Waiting
Container runtipi Healthy
Container runtipi-reverse-proxy Starting
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint runtipi-reverse-proxy (33a1ae9f4fc94f5e3ec91d6989e5ce2ccb048703f172f9765b1e54926b97e96a): Bind for 0.0.0.0:80 failed: port is already allocated
My port 80 indeed is already allocated because I'm running nginx proxy manager. It didn't seem to interfere until now but for some reason it seems to not be working anymore ? 😦
Nicolas
Nicolasβ€’3mo ago
Hello, this is probably a bug we introduced sorry about this. You can go back to 4.1.x safely for this time I’ll investigate asap Can you share your debug output before reverting?
frankynov
frankynovOPβ€’3mo ago
Bonjour Nicolas, There is the debut output attached in the first post, is it the one you are looking for ? It’s with current 4.2. So I can simply do a runtipi update v4.1.0 ?
Nicolas
Nicolasβ€’3mo ago
Ah sorry I missed it from my phone
frankynov
frankynovOPβ€’3mo ago
No worries. I just did a ./runtipi-cli update v4.1.1 and now it's reachable again. I'll wait for a bug fix, but if I can help and provide anything to help you, let me know πŸ™‚
Nicolas
Nicolasβ€’3mo ago
Can you try version v4.2.1 it should be fixed now
El Rato
El Ratoβ€’3mo ago
Im having the same problem with version 4.2.1, but with port 9090. There is nothing using that port
frankynov
frankynovOPβ€’3mo ago
For me it's solved with 4.2.1 πŸ‘ @El Rato - after you updated, there is a little table, does it show your IP and your 9090 port ? On 4.2.0 it was showing port 80 instead of 8080.
El Rato
El Ratoβ€’3mo ago
I'm not understanding which table you're talking about πŸ˜… The green one in the server terminal?
frankynov
frankynovOPβ€’3mo ago
Yes, like this :
No description
El Rato
El Ratoβ€’3mo ago
I dont even get that table, just the error. But ill just change the port to 9091 and see if it solves the issue

Did you find this page helpful?