supabase: AuthApiError: Error sending confirmation mail
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
Sometimes, the sign up function returns the following error:
AuthApiError: Error sending confirmation mail at handleError (webpack-internal:///(action-browser)/./node_modules/.pnpm/@supabase+gotrue-js@2.62.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:46:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async _handleRequest (webpack-internal:///(action-browser)/./node_modules/.pnpm/@supabase+gotrue-js@2.62.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:93:9) at async _request (webpack-internal:///(action-browser)/./node_modules/.pnpm/@supabase+gotrue-js@2.62.0/node_modules/@supabase/gotrue-js/dist/module/lib/fetch.js:73:18) at async SupabaseAuthClient.signUp (webpack-internal:///(action-browser)/./node_modules/.pnpm/@supabase+gotrue-js@2.62.0/node_modules/@supabase/gotrue-js/dist/module/GoTrueClient.js:236:23) at async signUp (webpack-internal:///(action-browser)/./src/app/cadastro/_actions/index.ts:26:17) at async project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\compiled\next-server\app-page.runtime.dev.js:39:406 at async t4 (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\compiled\next-server\app-page.runtime.dev.js:38:6379) at async rk (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\compiled\next-server\app-page.runtime.dev.js:39:25934) at async doRender (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:1394:30) at async cacheEntry.responseCache.get.routeKind (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:1555:28) at async DevServer.renderToResponseWithComponentsImpl (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:1463:28) at async DevServer.renderPageComponent (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:1856:24) at async DevServer.renderToResponseImpl (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:1894:32) at async DevServer.pipeImpl (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:911:25) at async NextNodeServer.handleCatchallRenderRequest (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\next-server.js:271:17) at async DevServer.handleRequestImpl (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\base-server.js:807:17) at async project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\dev\next-dev-server.js:331:20 at async Span.traceAsyncFn (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\trace\trace.js:151:20) at async DevServer.handleRequest (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\dev\next-dev-server.js:328:24) at async invokeRender (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\lib\router-server.js:163:21) at async handleRequest (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\lib\router-server.js:342:24) at async requestHandlerImpl (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\lib\router-server.js:366:13) at async Server.requestListener (project_folder\node_modules\.pnpm\next@14.1.0_@babel+core@7.23.7_react-dom@18.2.0_react@18.2.0\node_modules\next\dist\server\lib\start-server.js:140:13) { __isAuthError: true, status: 500 }
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
const res = await supabase.auth.signUp({ email, password })
if (res.error !== null) console.log({ signup_error: res.error })
Expected behavior
res.error should be null.
System information
- OS: Windows 10
- Browser Brave
- Version of @supabase/ssr: ^0.0.10
- Version of Node.js: v20.9.0
Additional context
I’m using Next.js and Supabase’s integration with Resend (as custom SMTP). It happens both on development and production, although in production there’s less trace log information.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 5
- Comments: 47 (3 by maintainers)
do not use stmp server ,just paid。 this error cost me a day to debug . try to delete this project and create new
I checked the API key in Resend, when I clicked on the “last used” cell, I could get to its logs. It said:
{ "name": "validation_error", "message": "The associated domain with your API key is not verified. Please, create a new API key with full access or with a verified domain.", "statusCode": 400 }So what I did is I created a full access api key and replaced the old password in Supabase with that. The problem was solved. The issue for us probably was that we used a “Sending access” api key.
Hey @eluchsinger @alissanguyen @roobox, I haven’t seen or had any users report this issue again since my original comment, but I also don’t have much logging set up and the Resend dashboard never reports any errors, so I guess it could still be happening occasionally.
This is what Resend told me after I reported the issue in March:
It might be worth raising a ticket if you haven’t done so yet?
Temporarily switching to Postmark did work for me previously, but I’d rather stay with Resend (if its reliability can be guaranteed…)
Maybe you can change your sender email with a domain that verifies in your email services, in my case I use Resend, and that fixed it
For me it turned out to actually be a problem with Resend.
I went to the “Logs” section in Resend and on the failed emails it said something like
Configuration set <xxxxxxxxxx> does not exist.But i’m still not sure what caused this, i contacted them but they were slow to reply. So i just deleted my domain in Resend and added it again and the error went away.
Hey same problem here. With Resend and also with other providers.
Also tried changing port to 587 or restarting the project. Nothing helped so far…
i’v got the same issue @ every signup
auth/v1/otp 500 (Internal Server Error)
We have same issue