Skip to content
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]: Setting a Public port on postgresql with supabase causes nginx:stable to constantly restart #5246

Open
gekkojelly opened this issue Feb 27, 2025 · 1 comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@gekkojelly
Copy link

Error Message and Logs

If we look at the logs for the nginix:stable-alpine container the following error will repeat every 10seconds or so:
docker logs 824452bb7de4
2025/02/27 16:19:24 [emerg] 1#1: host not found in upstream "postgresql-tggwgck84cgowk48k440sws0" in /etc/nginx/nginx.conf:12
nginx: [emerg] host not found in upstream "postgresql-tggwgck84cgowk48k440sws0" in /etc/nginx/nginx.conf:12
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: IPv6 listen already enabled
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up

Steps to Reproduce

  1. Install supabase resource, keep the defaults, click save & deploy.
  2. Against the postgresql container, click settings, set public port to: 5432, tick 'make it publicly available' & save.
  3. 'docker ps', shows a new container running nginix:stable-alpine which I assume will proxy my requests to postgresql and this container restarts every few seconds which I presume is why I am unable to connect over 5432.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.395

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Rocky Linux 9.5

Additional Information

I've tried 3-4 fresh supabase installations against two different servers and the error persists.

@gekkojelly gekkojelly added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Feb 27, 2025
@djsisson
Copy link
Contributor

@gekkojelly it looks like this recent change broke the detection, this used to return standalone-supabase/postgres, which would then set the correct container name of supabase-db-xxxx in the dbproxy start

if ($image->contains('postgres') || $image->contains('postgis')) {

however it now defaults to jsut return postgres, so gives the incorrect container name

there is a pr to fix some of this code, already, though not sure if that will refix it
#5175

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants