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

ERR_SSL_SSLV3_ALERT_HANDSHAKE_FAILURE: SDK fails to find authenticated user #1864

Closed
2 tasks done
selalipop opened this issue Dec 9, 2024 · 1 comment
Closed
2 tasks done
Labels
bug Something isn't working

Comments

@selalipop
Copy link

selalipop commented Dec 9, 2024

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

SDK fails to find authenticated user

TypeError: fetch failed
at Object.fetch (node:internal/deps/undici/undici:11372:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async _handleRequest (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:115:18)
at async _request (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:105:18)
at async eval (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:890:24)
at async SupabaseAuthClient._useSession (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:790:20)
at async SupabaseAuthClient._getUser (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:880:20)
at async eval (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:867:20)
at async eval (webpack-internal:///(rsc)/./node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:735:28) {
  cause: [Error: C03A08E801000000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake 
failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1586:SSL alert number 40
  ] {
    library: 'SSL routines',
   reason: 'sslv3 alert handshake failure',
   code: 'ERR_SSL_SSLV3_ALERT_HANDSHAKE_FAILURE'

To Reproduce

  1. Log into application
  2. View console

Expected behavior

Authenticated user is fetched.

Screenshots

N/A

System information

"@supabase/auth-helpers-nextjs": "^0.8.1",
"@supabase/auth-helpers-react": "0.4.2",
"@supabase/auth-ui-react": "0.4.2",
"@supabase/auth-ui-shared": "0.1.6",
"@supabase/postgrest-js": "1.9.2",
"@supabase/ssr": "0.0.10",
"@supabase/supabase-js": "2.33.1",

Additional context

@selalipop selalipop added the bug Something isn't working label Dec 9, 2024
@cstockton
Copy link
Contributor

It is a very generic error indicating a handshake failure occurred, without saying what part of the handshake failed. There isn't much we can do here from our side, the auth server doesn't have built in tls support.

If this is for a Supabase project you will want to open a support ticket so we can investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants