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]: Supabase Public schema not publicly available #2861

Open
olsoda opened this issue Jul 17, 2024 · 6 comments · May be fixed by #4598
Open

[Bug]: Supabase Public schema not publicly available #2861

olsoda opened this issue Jul 17, 2024 · 6 comments · May be fixed by #4598

Comments

@olsoda
Copy link

olsoda commented Jul 17, 2024

Description

Screenshot 2024-07-17 at 11 34 56 AM
Brand new Supabase deploy, shows this in API docs. Same thing no matter if in Supabase Db service a port is set and marked as "Make it publicly available" or not.

Similarly, when viewing the logs in the Supabase dashboard, get a 502 error. Not sure if it's related, but guessing it is if there's an issue hitting Postgres
Screenshot 2024-07-17 at 11 39 48 AM

Minimal Reproduction (if possible, example repository)

Latest Coolify, new resource, Supabase, deploy.

Exception or Error

No response

Version

4.0.0 beta 315

@feavel1
Copy link

feavel1 commented Jul 18, 2024

Interesting, I wanted to switch from Vercel to self-hosted Coolify using Supabase and Svelte-Kit for a long time now. Will probably look into the issue that you have. If possible, you can post any helpful information that is related.

@feavel1
Copy link

feavel1 commented Jul 18, 2024

By reading what you have posted, this might be related to Supabase dashboard connection it self. I guess you are not using self-hosted Supabase?

@mavdmichael
Copy link

I sadly have somewhat the same issue,
Coolify beta 317 on one server, with several remote servers connected. One of these servers currently has Supabase one-click and Logto one-click installed.

The supabase db in the supabase stack has the following port settings, but it refuses to connect externally
image

And the LogTo db is the same
image

Checking or unchecking the make public checkbox has no bearing.

I've disabled ufw and the hosting provider has no firewall rules in place.

on the same server in a different project, I have a standalone Postgres one-click, whit the following
image

and this does work and allows external connections just fine.

@mavdmichael
Copy link

mavdmichael commented Jul 22, 2024

I want to add to this that the issue seems to be that adding a public port starts an nginx [stackid]-proxy, but it fails to start.
And keeps restarting over and over.

Perhaps conflicting with each other or the traefik one.

image

Managed to capture one during the second it was started before exiting.
image

And it tries to listen to the 80/tcp just like traefik.

edit:
managed to get the logs from the nginx that keeps restarting;
`docker logs a41294c71a69

/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: Getting the checksum of /etc/nginx/conf.d/default.conf
10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
/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
2024/07/22 07:55:06 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:07 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:07 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:08 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:09 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:11 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:15 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" 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
2024/07/22 07:55:21 [emerg] 1#1: invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12
nginx: [emerg] invalid port in upstream "wcgsg44:" in /etc/nginx/nginx.conf:12`

@olsoda
Copy link
Author

olsoda commented Jul 23, 2024

Interesting @mavdmichael -- have you found any workaround yet?

@mavdmichael
Copy link

Interesting @mavdmichael -- have you found any workaround yet?

I did. And it was too simple.

I just put a ports: section in the docker-compose file for the db service.

image

image

and that did the trick.

@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Jan 9, 2025
@peaklabs-dev peaklabs-dev linked a pull request Jan 9, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants