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

Update to Latest supabase 1.25.02#7709e8d #40

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

malko
Copy link
Contributor

@malko malko commented Mar 26, 2025

This will update supabase template to latest version (ie: 1.25.02#7709e8d), this will notably add supavisor.

Copy link

github-actions bot commented Mar 26, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
templates ✅ Ready (View Log) Visit Preview eeec4b4

image: supabase/supavisor:2.4.14
restart: unless-stopped
ports:
- ${POSTGRES_PORT}:5432

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is causing this error, commenting this works correctly:

Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint meu-projeto-supabase-hs6i9o-supavisor-1 (): Bind for 0.0.0.0:5432 failed: port is already allocated

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird worked on my side will try to reproduce tonight

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@djin-lucas Did you change some settings from the default config ? I've just tried again a fresh deploy on a new project without this issue, the only settings i've changed from the default for first run was API_EXTERNAL_URL and SUPABASE_PUBLIC_URL

Accessing from another host using the connection strings as described here works for session based and pooled connections.

Is it possible that the problem may be related to you having another service running on that port ? If this is the case can you try to change the env value of
POSTGRES_PORT=5432
POOLER_PROXY_PORT_TRANSACTION=6543

@malko
Copy link
Contributor Author

malko commented Mar 27, 2025

I passed it in draft as for now we still faces an issue with gotrue that won't send mails this is related to GOTRUE_MAILER_EXTERNAL_HOSTS apparently but even adding this env var doesn't seems to solve the problem

@malko
Copy link
Contributor Author

malko commented Mar 27, 2025

posted an issue in the gotrue repository about that supabase/auth#1970

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 this pull request may close these issues.

None yet

2 participants