Runtipi•2w 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

32 Replies

Nicolas•2w ago

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

ChandooOP•2w ago

okay , sure i will

ChandooOP•2w 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•2w ago

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

ChandooOP•2w ago

if i restart reverse proxy manually it works

message.txt

Nicolas•2w 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•2w 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•2w 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•2w ago

logs look clean

ChandooOP•2w ago

let me restart and see that will happen

message.txt

ChandooOP•2w ago

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

Nicolas•2w ago

Yes!

ChandooOP•2w 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•2w ago

ChandooOP•2w ago

Nicolas•2w ago

docker logs runtipi-reverse-proxy

ChandooOP•2w ago

container is not running

Nicolas•2w ago

docker ps shows more info?

ChandooOP•2w ago

Nicolas•2w ago

or docker inspect runtipi-reverse-proxy

ChandooOP•2w ago

restart works

Nicolas•2w ago

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

ChandooOP•2w ago

Correct

Nicolas•2w 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•2w 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•2w 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•2w ago

ChandooOP•7d 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•7d 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

Gaming

Programming

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

Did you find this page helpful?