Runtipi•3mo ago

error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.2:5672 Error: connect ECONNREFUSED 1

I am upgrading to v4.4.0 it went through sucessfully, but failed to start with RabbitMQ error I stopped runtipi, did system prune removed all the images and did fresh pull, i am still having the same issue. let me know if anyone having resolution for this. Looks like it is always scary and tricky to update RunTipi

48 Replies

Nicolas•3mo ago

Please follow the Example post so we can help you It's always tricky to help without any further info

ChandooOP•3mo ago

okay , sure i will

ChandooOP•3mo ago

} Current branch: master
2025-09-20T13:17:05.607Z - debug >      Target SHA: 1f683fc2d9767521284c8f0a464c285b8dea943e
2025-09-20T13:17:07.032Z - 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:1637:16)
2025-09-20T13:17:07.033Z - warn >       RabbitMQ connection lost, attempting to reconnect...
2025-09-20T13:17:11.036Z - 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:1637:16)
2025-09-20T13:17:11.037Z - warn >       RabbitMQ connection lost, attempting to reconnect...
2025-09-20T13:17:17.856Z - info >       Connected to the queue
2025-09-20T13:17:19.091Z - info >       Connected to the queue
2025-09-20T13:17:19.579Z - info >       Connected to the queue
2025-09-20T13:17:19.628Z - debug >      Repo https://github.com/runtipi/runtipi-appstore already exists
2025-09-20T13:17:21.203Z - info >       Connected to the queue

} Current branch: master
2025-09-20T13:17:05.607Z - debug >      Target SHA: 1f683fc2d9767521284c8f0a464c285b8dea943e
2025-09-20T13:17:07.032Z - 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:1637:16)
2025-09-20T13:17:07.033Z - warn >       RabbitMQ connection lost, attempting to reconnect...
2025-09-20T13:17:11.036Z - 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:1637:16)
2025-09-20T13:17:11.037Z - warn >       RabbitMQ connection lost, attempting to reconnect...
2025-09-20T13:17:17.856Z - info >       Connected to the queue
2025-09-20T13:17:19.091Z - info >       Connected to the queue
2025-09-20T13:17:19.579Z - info >       Connected to the queue
2025-09-20T13:17:19.628Z - debug >      Repo https://github.com/runtipi/runtipi-appstore already exists
2025-09-20T13:17:21.203Z - info >       Connected to the queue

message.txt

Nicolas•3mo ago

Thanks can you also paste the result of ./runtipi-cli debug?

ChandooOP•3mo ago

if i restart reverse proxy manually it works

message.txt

Nicolas•3mo ago

I see you have a custom user-config/tipi-compose.yml which is probably what's breaking the default here, could you also share what custom changes you have applied? Same for the custom traefik config Or at least try to disable first these two customizations and see if runtipi works properly without your changes

ChandooOP•3mo ago

tipi-compose.yml

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DUCKDNS_TOKEN=XXXXXXXXXXXXXXXXXXXXX

services:
  runtipi-reverse-proxy:
    ports:
      - 8080:8080
    environment:
      - DUCKDNS_TOKEN=XXXXXXXXXXXXXXXXXXXXX

i remember facing same issue a while ago after upgrade. not sure what I did. setings.json

{
  "internalIp": "192.168.99.140",
  "appsRepoUrl": "https://github.com/runtipi/runtipi-appstore",
  "domain": "yog.duckdns.org",
  "appDataPath": "/home/runtipi/runtipi",
  "localDomain": "tipi.local",
  "guestDashboard": false,
  "allowAutoThemes": true,
  "allowErrorMonitoring": false,
  "persistTraefikConfig": true,
  "port": 80,
  "sslPort": 443,
  "listenIp": "192.168.99.140",
  "timeZone": "America/New_York",
  "eventsTimeout": 5,
  "advancedSettings": true,
  "forwardAuthUrl": "http://runtipi:3000/api/auth/traefik",
  "logLevel": "debug",
  "themeBase": "gray",
  "themeColor": "lime"
}

{
  "internalIp": "192.168.99.140",
  "appsRepoUrl": "https://github.com/runtipi/runtipi-appstore",
  "domain": "yog.duckdns.org",
  "appDataPath": "/home/runtipi/runtipi",
  "localDomain": "tipi.local",
  "guestDashboard": false,
  "allowAutoThemes": true,
  "allowErrorMonitoring": false,
  "persistTraefikConfig": true,
  "port": 80,
  "sslPort": 443,
  "listenIp": "192.168.99.140",
  "timeZone": "America/New_York",
  "eventsTimeout": 5,
  "advancedSettings": true,
  "forwardAuthUrl": "http://runtipi:3000/api/auth/traefik",
  "logLevel": "debug",
  "themeBase": "gray",
  "themeColor": "lime"
}

Nicolas•3mo ago

You told that after restarting the reverse proxy it was working. Maybe what are the logs of it? docker logs runtipi-reverse-proxy it seems stuck in "Created" state

ChandooOP•3mo ago

logs look clean

ChandooOP•3mo ago

let me restart and see that will happen

message.txt

ChandooOP•3mo ago

i am restarting with sudo that is the way to do right?

Nicolas•3mo ago

Yes!

ChandooOP•3mo ago

2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> Deprecated features: `transient_nonexcl_queues`: Feature `transient_nonexcl_queues` is deprecated.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> By default, this feature can still be used for now.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> Its use will not be permitted by default in a future minor RabbitMQ version and the feature will be removed from a future major RabbitMQ version; actual versions to be determined.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> To continue using this feature when it is not permitted by default, set the following parameter in your configuration:
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0>     "deprecated_features.permit.transient_nonexcl_queues = true"
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> To test RabbitMQ as if the feature was removed, set this in your configuration:
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0>     "deprecated_features.permit.transient_nonexcl_queues = false"

2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> Deprecated features: `transient_nonexcl_queues`: Feature `transient_nonexcl_queues` is deprecated.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> By default, this feature can still be used for now.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> Its use will not be permitted by default in a future minor RabbitMQ version and the feature will be removed from a future major RabbitMQ version; actual versions to be determined.
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> To continue using this feature when it is not permitted by default, set the following parameter in your configuration:
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0>     "deprecated_features.permit.transient_nonexcl_queues = true"
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0> To test RabbitMQ as if the feature was removed, set this in your configuration:
2025-09-20 13:37:26.941251+00:00 [warning] <0.681.0>     "deprecated_features.permit.transient_nonexcl_queues = false"

same issue proxy not started

--- Docker containers ---
┌───────────────────────┬───────────────────────────────┐
│ runtipi-reverse-proxy │ Created                       │
│ runtipi               │ Up About a minute (unhealthy) │
│ runtipi-db            │ Up 2 minutes (healthy)        │
│ runtipi-queue         │ Up 2 minutes                  │
└───────────────────────┴───────────────────────────────┘

--- Docker containers ---
┌───────────────────────┬───────────────────────────────┐
│ runtipi-reverse-proxy │ Created                       │
│ runtipi               │ Up About a minute (unhealthy) │
│ runtipi-db            │ Up 2 minutes (healthy)        │
│ runtipi-queue         │ Up 2 minutes                  │
└───────────────────────┴───────────────────────────────┘

ChandooOP•3mo ago

ChandooOP•3mo ago

Nicolas•3mo ago

docker logs runtipi-reverse-proxy

ChandooOP•3mo ago

container is not running

Nicolas•3mo ago

docker ps shows more info?

ChandooOP•3mo ago

Nicolas•3mo ago

or docker inspect runtipi-reverse-proxy

ChandooOP•3mo ago

restart works

Nicolas•3mo ago

And after restart, everything works correctly? Like you can use runtipi?

ChandooOP•3mo ago

Correct

Nicolas•3mo ago

Okay so it's not an issue with runtipi-queue (and we can see in the logs that rabbitmq connects after a couple of tries)

ChandooOP•3mo ago

do i have to make any changes to the docker compose to me it looks like MQ should run after all the services are up

Nicolas•3mo ago

Something is preventing traefik to start, maybe your custom config? Can you backup the traefik folder at the root (rename to traefik_bak) and in your runtipi settings disable persistTraefikConfig Then try to restart

ChandooOP•3mo ago

okay i will try and update @Nicolas it didnt help, i removed all settings and tipi-compse and restarted , it still has the same issue. is there any way i can open a BUG not sure what to capture

Nicolas•3mo ago

I'm not sure what could be wrong here If you could describe reproductions steps on a clean OS with minimal config it could help

ChandooOP•3mo ago

@Nicolas After so many irritating days of dealing with runtipi. I found the problem. after upgrade for some reason traefik.yml config was overwritten. corrected it and trying to restart let me see what happens

Nicolas•3mo ago

Sorry you have experienced this, it should not happen if persistTraefikConfig is set to true. Did it happen for you even with that option enabled?

ChandooOP•3mo ago

it was set to true i corrected the traefik.yml no luck i am still having issue. proxy container is failing to start with ./runtipi-cli. manually it works I am thinking of scrapping every thing start fresh certs are not generated as well for new apps 2025-10-04T18:20:58Z ERR Error renewing certificate from LE: {yog.duckdns.org []} error="error: one or more domains had a problem:\n[yog.duckdns.org] propagation: time limit exceeded: last error: authoritative nameservers: DNS call error: read udp 172.18.0.5:54028->15.223.21.81:53: i/o timeout [ns=ns7.duckdns.org.:53, question='_acme-challenge.yog.duckdns.org. IN TXT']\n" acmeCA=https://acme-v02.api.letsencrypt.org/directory providerName=myresolver.acme if i delete acme.json will it generate automatically? something wrong with acme.json, i renamed it , all the services came through without issue

Nicolas•3mo ago

Kind of strange I have experienced recently a very similar issue, i had some wrong configs in traefik.yml and it wouldn’t start anymore Do you know what was wrong with the config? What did you have to change? I had no logs, no errors in traefik

ChandooOP•3mo ago

it went to default all my settings were lost i am redoing every thing now clean up and fresh install debugging further doesnt make sense to me if runtipi is stable, This is game changer in home lab.

Nicolas•3mo ago

I’ll try a few things on my side

ChandooOP•3mo ago

you should keep runtipi seperate from the apps. deleting the folder will delete all the apps. If ppl want to do fresh install of runtipi for somereasonthey should have option to delete just runtipi and keep the settings in place and fresh runtipi should pickup them up i see persistTraficConfig default value is true. so i dont need to make any entries into settings.json right? i made my changes and proxy is failing to start

Nicolas•3mo ago

What have you changed? Probably traefik doesn’t like something This should not be the case

Nicolas•3mo ago

I installed from scratch and it's not the case

ChandooOP•3mo ago

that worked looks like you shouldn't touch settings.json i made change to traefik it failed

ChandooOP•3mo ago

all i did was create tipi-compose and made changes in traefik

Nicolas•3mo ago

Yes but what changes in traefik This is a traefik issue not being able to load something, so I suspect the changed config

InfBoumcyCastle•2mo ago

maybe a similar error i have in 4.5.5 (i think was also in 4.4.0 (no logs here)

InfBoumcyCastle•2mo ago

logs

message.txt

InfBoumcyCastle•2mo ago

happens when i restart the host with runtipi on it (after update f.i.) a sudo ./runtipi-cli restart helps

Gaming

Programming

error > RabbitMQ connection error connect ECONNREFUSED 172.18.0.2:5672 Error: connect ECONNREFUSED 1

Did you find this page helpful?