D
Dokploy2mo ago
labulac

deployment issues

During the deployment process using curl -sSL https://dokploy.com/install.sh | sh, I found that dokploy cannot connect to postgres.It's pointing to the wrong address10.0.1.8.But the correct IP is actually 10.0.1.9. After some trials and reviewing the source code, I found that the possible issue might be due to directly accessing dokploy-postgres, which led to resolving to 10.0.1.8. However, by pinging dokploy-postgres.1.xxxxxxxxxxxxxxxxxxxxxxxxx, it can correctly access postgres. I'm not sure if this is the issue, please help to take a look.
No description
No description
No description
6 Replies
Siumauricio
Siumauricio2mo ago
using proxmox?
labulac
labulacOP2mo ago
Installed LXC directly on Debian, and then used dokploy within the LXC.
Siumauricio
Siumauricio2mo ago
I think this problem is more related to docker swarm and how your network is configured internally, but it has nothing to do with dokploy itself. https://docs.dokploy.com/docs/core/manual-installation you can see all the enviroment variables that you can pass to dokploy container
Manual Installation | Dokploy
Learn how to manually install Dokploy on your server.
Siumauricio
Siumauricio2mo ago
You can try passing the DATABASE_URL, with that internal ip and see if it works for you.
labulac
labulacOP2mo ago
thanks, It might be an issue with my lxc environment . because on a Google Cloud AMD machine, I can normally complete the deployment using curl -sSL https://dokploy.com/install.sh | sh.
Siumauricio
Siumauricio2mo ago
you are the same from this issue https://github.com/Dokploy/dokploy/issues/1698?
GitHub
Dokploy stack routing issue when using internal only deployments ·...
To Reproduce Create LXC container or VM with ubuntu/debian image. Install dokploy, first set the environment variable matching the LXC container IP (we don't want WAN IP for swarm): export ADVE...

Did you find this page helpful?