Limetta icon indicating copy to clipboard operation
Limetta copied to clipboard

SASL_SIGNATURE_MISMATCH after initial install

Open harperaa opened this issue 1 year ago • 0 comments

Issue installing locally.

I am new to supabase, but followed your directions, after setting up a project and gaining the connection string and password from supabase console.

Connection string is different than what you had in the .env.sample file... it looks like: postgresql://postgres.[redacted]:[YOUR-PASSWORD]@aws-0-us-east-1.pooler.supabase.com:6543/postgres

Of course, I used the project password in above connection string.

After issuing pnpm db:push, I get the following output, which looks good, but I am not sure. $ pnpm db:push

[email protected] db:push /Users/harperaa/Dropbox/code/Limetta drizzle-kit push

drizzle-kit: v0.21.2 drizzle-orm: v0.30.10

No config path provided, using default path Reading config file '/Users/harperaa/Dropbox/code/Limetta/drizzle.config.ts' Using 'pg' driver for database querying [i] No changes detected

But then, after attempting to login the first time, on either google or github oauth, I get the following error.

  • event compiled successfully in 134 ms (1863 modules) [next-auth][warn][NEXTAUTH_URL] https://next-auth.js.org/warnings#nextauth_url (node:41681) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification. (Use node --trace-warnings ... to show where the warning was created) [next-auth][error][adapter_error_getUserByAccount] https://next-auth.js.org/errors#adapter_error_getuserbyaccount SASL_SIGNATURE_MISMATCH: The server did not return the correct signature { message: 'SASL_SIGNATURE_MISMATCH: The server did not return the correct signature', stack: 'Error: SASL_SIGNATURE_MISMATCH: The server did not return the correct signature\n' + ' at SASLFinal (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:480:87)\n' + ' at Authentication (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:450:206)\n' + ' at handle (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:337:728)\n' + ' at Socket.data (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:225:17)\n' + ' at Socket.emit (node:events:518:28)\n' + ' at addChunk (node:internal/streams/readable:561:12)\n' + ' at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)\n' + ' at Readable.push (node:internal/streams/readable:392:5)\n' + ' at TCP.onStreamRead (node:internal/stream_base_commons:189:23)\n' + ' at TCP.callbackTrampoline (node:internal/async_hooks:130:17)', name: 'Error' } [next-auth][error][OAUTH_CALLBACK_HANDLER_ERROR] https://next-auth.js.org/errors#oauth_callback_handler_error SASL_SIGNATURE_MISMATCH: The server did not return the correct signature Error: SASL_SIGNATURE_MISMATCH: The server did not return the correct signature at SASLFinal (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:480:87) at Authentication (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:450:206) at handle (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:337:728) at Socket.data (webpack-internal:///(rsc)/./node_modules/.pnpm/[email protected]/node_modules/postgres/src/connection.js:225:17) at Socket.emit (node:events:518:28) at addChunk (node:internal/streams/readable:561:12) at readableAddChunkPushByteMode (node:internal/streams/readable:512:3) at Readable.push (node:internal/streams/readable:392:5) at TCP.onStreamRead (node:internal/stream_base_commons:189:23) at TCP.callbackTrampoline (node:internal/async_hooks:130:17) { name: 'GetUserByAccountError', code: 'SASL_SIGNATURE_MISMATCH' }

harperaa avatar Nov 12 '24 21:11 harperaa