sweatybridge
commented
7 months ago Could you try running npx supabase link without debug flag? SSL cannot be enabled in debug mode at the moment.
Closed bizz84 closed 7 months ago
sweatybridge
commented
7 months ago Could you try running npx supabase link without debug flag? SSL cannot be enabled in debug mode at the moment.
webdevleo
commented
7 months ago Could you try running
npx supabase linkwithout debug flag? SSL cannot be enabled in debug mode at the moment.
Thanks for you answer. It solved the issue
peterkos
commented
1 month ago For anyone else coming to here from a search, updating to the latest supabase CLI 1.187.8 fixed the issue for myself on a similar error w/ brew :)
Also noted here: https://github.com/orgs/supabase/discussions/21058
aradhya-variational-io
commented
1 month ago seeing the same issue, updating supabase CLI didnt help
wemgl
commented
1 month ago I'm on supabase CLI version 1.187.10 (the latest version at the time of this comment) and I'm still having this issue. Here's a portion of the logs I see when I run supabase db pull --debug in my terminal:
2024/08/06 08:06:41 Connect Start: tcp [REDACTED]:5432
2024/08/06 08:06:41 Connect Done: tcp [REDACTED]:5432
2024/08/06 08:06:41 PG Send: {"Type":"StartupMessage","ProtocolVersion":196608,"Parameters":{"database":"postgres","user":"postgres.[REDACTED]"}}
2024/08/06 08:06:41 PG Recv: {"Type":"ErrorResponse","Severity":"FATAL","SeverityUnlocalized":"FATAL","Code":"XX000","Message":"SSL connection is required","Detail":"","Hint":"","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"","Line":0,"Routine":"","UnknownFields":null}
failed to connect to postgres: failed to connect to `host=aws-0-us-east-1.pooler.supabase.com user=postgres.[REDACTED] database=postgres`: server error (FATAL: SSL connection is required (SQLSTATE XX000))What's interesting is that I see this when I run the aforementioned comment without the debug flag:
failed to connect to postgres: failed to connect to `host=127.0.0.1 user=postgres database=postgres`: dial error (dial tcp 127.0.0.1:54320: connect: connection refused)Note that the log line mentions the database running on my local machine and not the pooler.supabase.com one. Any ideas? I also realized that I have SSL Enforcement enabled on the database for my project, but I'd rather not disable it at the moment.
sweatybridge
commented
1 month ago dial error (dial tcp 127.0.0.1:54320: connect: connection refused)
This is indicative of an error connecting to shadow database. Do you have docker host networking enabled in settings?
The --debug flag is not compatible with ssl so the other error is not really actionable.
wemgl
commented
1 month ago @sweatybridge I was actually using colima and I think that contributed to the error I was having. I stopped it, switched over to using the macOS Docker app, and then ran the supabase db pull command again and it finally worked.
Describe the bug
In order to apply DB migrations, I run this custom build command on Vercel:
This was working for a long time. But since 20th Feb 2024, the Vercel build fails with:
I believe this is related to this discussion, which says:
We have also tried to create the
POSTGRES_URLvariable and pass the right URL there, but the problem is thatsupabase linkdoesn't use it, but it's used for migrations. But migrations can't be processed without the linked project.Screenshots All my Vercel builds have started failing since 20th Feb 2024:
System information
Vercel build log
``` [12:13:58.221] Running build in Washington, D.C., USA (East) – iad1 [12:13:58.344] CloningAdditional context
I see this in the log:
My
package.json:How should we configure Vercel so that
npx supabase linkstarts working again in light of the changes introduced here?https://github.com/orgs/supabase/discussions/17817