OTP server error

Open
#1,797 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, node.js

Research direction

Start by reproducing the failure at auth/v1/otp, both through signInWithOtp() and the Supabase dashboard's Send magic link action. Check the reported Supabase JS 2.39.7 and Node.js 20.16.0 environment, then trace the server-side error producing the 500 response. Done means a magic link is sent successfully instead of returning the reported error.

Written by the indexing model from the issue text.

Description

bug

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

auth/v1/otp is returning 500 error message: "Error sending magic link email", it doesn't matter if is through my application calling supabaseService.getClient().auth.signInWithOtp() nor trying to send it directly via the Supabase dashboard.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Go to 'Authentication'
  2. Click on 'Users'
  3. Select and click at any user
  4. Scroll down to 'Send magic link'
  5. Click on 'Send magic link'
  6. See error "Failed to send magic link: failed to make magiclink request: Error sending magic link email"

Expected behavior

A magic link to be sent to the user's e-mail

Screenshots

Not applicable

System information

  • OS: Windows 11
  • Microsoft Edge
  • Version of supabase-js: 2.39.7
  • Version of Node.js: 20.16.0
Dominant language
Go
Stars
2.6k
Forks
764
Avg merge
5d 3h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/auth

All issues in supabase/auth

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.