Fail to connect Redis

[ErickJ3]

I'm having some errors when running on pure Ubuntu 20, the VM is inside a Proxmox and the installation was completely clean

Redis Started ✅
Make sure you have installed Redis and it is running. Error: connect ECONNREFUSED 10.0.1.7:6379
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '10.0.1.7',
  port: 6379
}

From what I saw the error is only happening in the redis connection

CONTAINER ID   IMAGE                    COMMAND                  CREATED         STATUS         PORTS                                                                                                                 NAMES
f308e8ec89e7   dokploy/dokploy:latest   "docker-entrypoint.s…"   4 minutes ago   Up 4 minutes   0.0.0.0:3000->3000/tcp, :::3000->3000/tcp                                                                             dokploy.1.el9f89p18bsnjzjwf36lkxifo
61359c8372c3   postgres:16              "docker-entrypoint.s…"   5 minutes ago   Up 5 minutes   5432/tcp                                                                                                              dokploy-postgres.1.e3ts8ffqu4ne35m8wjrs2w5vi
6a524e60c957   redis:7                  "docker-entrypoint.s…"   5 minutes ago   Up 5 minutes   6379/tcp                                                                                                              dokploy-redis.1.s77na4xwwkmx17qz5mknah4px
709a4eb0c1f6   traefik:v2.5             "/entrypoint.sh trae…"   5 minutes ago   Up 5 minutes   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp   dokploy-traefik.1.d5jjok4v6om9osz8gyzmjz1zi

[Siumauricio]

Run the following command docker service update dokploy --image dokploy/dokploy:latest or you can go to /dashboard/settings/server/ scroll down and click on server and then reload and see the if the errors are still happening?

[luispoliveira]

I have exactly the same problem. Running on a VM inside Proxmox.

[Siumauricio]

Hmm probably is a thing of how Proxmox handles the internal dns resolution

https://github.com/Dokploy/dokploy/blob/3f9e1381b688e8450a0735b59278d557697cff36/server/queues/queueSetup.ts#L4

[luispoliveira]

Update: The error appears on a CT instance, but if you create a VM it works fine.

[ErickJ3]

Well, the problem is actually running inside a CT. If it runs inside the VM, everything works normally. I will investigate a little more to try some solution for the beginning in CT. Therefore, the issue can be closed