SASL_SIGNATURE_MISMATCH: The server did not return the correct signature
Problem
Bug report - [ ] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug I recently switched from a local postgres database to supabase and using drizzle as the ORM. This is the drizzle configuration (the app is a discord bot, so long-running) [code block] EDIT: All these throw a connection error, whether it is `pg` or `postgres` [code block] On the first request to the database I get the following: [code block] However, if use a connection string with the exact same values (env variables joined in the format of the connection string) the connection works. I'd prefer to use the object notation in the `postgres()` connection options To Reproduce Source code can be found here <https://github.com/noook/discord-mbti> Expected behavior Object notation should behave the same as the connection string Screenshots Database connection on supabase dashboard <img width="893" alt="image" src="https://github.com/supabase/supabase/assets/19751938/bb29b5fa-55f6-4e8b-8f2c-197ee4ed7a84"> System information - OS: Linux (docker) - Version of supabase-js: not used - bun 1.0.29 Additional context -
Error Output
error app-1 | 34 | }
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: SASL_SIGNATURE_MISMATCH: The server did not return the correct signature
sorry to necro your closed issue but since it was not really resolved with documentation i hope you wont mind. for anyone else stumbling here during troubleshooting, I confirmed that this issue is likely caused by a version mismatch between the client's pg version(I tested 14) and the remote (v15 as of now). I'm not sure why it isn't observed in psql (which will warn about the outdated client an
Trust Score
4 verifications
- 1
sorry to necro your closed issue but since it was not really resolved with docum
sorry to necro your closed issue but since it was not really resolved with documentation i hope you wont mind.
- 2
for anyone else stumbling here during troubleshooting, I confirmed that this iss
for anyone else stumbling here during troubleshooting, I confirmed that this issue is likely caused by a version mismatch between the client's pg version(I tested 14) and the remote (v15 as of now).
- 3
I'm not sure why it isn't observed in psql (which will warn about the outdated c
I'm not sure why it isn't observed in psql (which will warn about the outdated client and _does_ confirm TLS) or why so many people seem to be running into this at once. So, it does seem to be an issue with either Drizzle or possibly the database driver. You can, as @encima suggested, disable SSL as a workaround but in any case, it's ideal to upgrade your client if its outdated. (and resolve the SSL issues as a win-win…)
Validation
Resolved in supabase/supabase GitHub issue #21690. Community reactions: 6 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep