-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: connection to server at "postgres" port 5432 failed #5160
Comments
This will happen if your compose has a service with the name postgres and you add it to the coolify network, since there is already an existing service with that name docker dns will alternate between the two To solve either do not put your project in the coolify network or rename the postgre service in your compose. You will need to stop the extra postgres container in the coolify network Run docker ps to get the id you need to stop |
Thank you so much ! I managed to stop the new project in the UI with a bit of refreshing. Do you know if there is an issue about validating a docker compose to avoid this issue ? |
Oh, nice catch. I can easily fix this but setting the default I will test it and add it to the next version if everything works. |
Error Message and Logs
After deploying a docker compose app, the coolify instance got a lot of issues with PostgreSQL
Steps to Reproduce
I deployed a docker compose app with Nextjs + Postgresql and then got the issue.
All deployed apps are okay but I'm stuck outside of the Coolify instance sadly.
Sometimes on refresh I can do some actions but got a 500 error really fast, either in a modal or full page.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.390
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 10 (buster)
Additional Information
No response
The text was updated successfully, but these errors were encountered: