[CLI] Persistent "Failed SASL Auth" in VS Code after All Troubleshooting

[Yurii108]

Describe the bug

I'm unable to connect to my Supabase projects using the CLI. I am receiving different "failed SASL auth" errors for my dev and production environments, even after trying all common troubleshooting steps.

• Production Project (guxytmziogdkitbaqymu): The supabase link command fails with the error "invalid SCRAM server-final-message received from server."
• Dev Project (ebmywyqhaqffqturiyzl): The supabase link command fails with a "password authentication failed for user 'postgres'" error.

These errors persist even after resetting passwords and completely clearing my local environment.

To Reproduce

1. I have fully cleaned my local environment by deleting ~/.supabase and the local supabase project directory.
2. I have also reset the database password on the Supabase dashboard for both the dev and production projects.
3. I run pnpx supabase link and select either the dev or prod project from the list.
4. The command fails with one of the two errors mentioned above, depending on which project is selected.

Expected behavior

The supabase link command should successfully authenticate and connect my local environment to the selected Supabase project, allowing me to run supabase db pull or supabase db push as intended.

Screenshots

• Initial supabase link prompt: (You can attach the image image_1)
• Errors after trying to link: (You can attach the image image_2 which shows both errors)
• Version check showing a recent update: (You can attach the image image_fa452d.png to show your version is up to date)

System information

• OS: [Your Operating System (e.g., Windows 11)]
• Browser (if applies): [Chrome]
• Supabase CLI Version: [2.39.2]
• Node.js Version: [v20.10.0]
• Editor: VS Code

Additional context

• I have tried resetting passwords on the Supabase dashboard multiple times for both projects.
• I have logged out and logged in via the CLI using pnpx supabase logout and pnpx supabase login.
• I have tried clearing the pnpx cache with pnpm store prune.
• I have manually checked for and deleted any cached credentials in Windows Credential Manager.
• The issue seems to be specific to my local machine, as my projects are working for other team members.

I am very grateful for any help in this situation. I have been trying to solve this problem for several days and it significantly affects my work. Your help will be very important to me.

[greatwitenorth]

I'm having the same issue. I've tried all the troubleshooting from this issue as well.

[Yurii108]

@greatwitenorth I don't know how to correctly transfer the changes from dev to prod. Right now, I also have the idea to write to the Supabase support

[Hallidayo]

Transferred from supabase repo.

[virtual-college-coach]

Hello - I am having the same issue when trying to deploy in my github actions but only in some environments (see this issue here). Any updates? This is significantly impacting the launch of my product.

[greatwitenorth]

Can anyone from supabase team help with this?

[fiizzy]

Also having this issue. Any progress here?