# Error 500 on supabase forgot password

**URL:** <https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613>\
**Category:** Ask us anything\
**Tags:** authentication, supabase\
**Created:** [September 16, 2024, 3:31am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613 "2024-09-16T03:31:39Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![liweihan](https://avatars.discourse-cdn.com/v4/letter/l/a6a055/32.png) [@liweihan](https://community.weweb.io/u/liweihan)\
**Post date:** [September 16, 2024, 3:31am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/1 "2024-09-16T03:31:39Z")

</div>

I got the following error 500, while executing the Supabase Forgot Password workflow on form submission, the same code has working for months, just got a few report by our customers today and I can reproduce it 100%.

name: “Error”

stack: “Error: Error sending recovery email at Object.resetPasswordForEmail ([https://cdn.weweb.io/components/1fa0dd68-5069-436c-9a7d-3b54c340f1fa/0ed9be68-23fd-457e-a170-a4ca83d66da5/dist/manager.js:1:158761](https://cdn.weweb.io/components/1fa0dd68-5069-436c-9a7d-3b54c340f1fa/0ed9be68-23fd-457e-a170-a4ca83d66da5/dist/manager.js:1:158761)) at async S ([https://editor-cdn.weweb.io/public/js/index.698cb60a.js:1:426380](https://editor-cdn.weweb.io/public/js/index.698cb60a.js:1:426380))”

message: “Error sending recovery email”

cause

\_\_isAuthError: true

name: “AuthApiError”

status: 500

code: “unexpected\_failure”

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 16, 2024, 6:57am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/2 "2024-09-16T06:57:25Z")

</div>

In the Network tab you should find a better log, otherwise in Supabase ad well. If you post it here, we might be able to help

---

<div class="post-metadata">

**Author:** ![codingjohn](https://avatars.discourse-cdn.com/v4/letter/c/96bed5/32.png) [@codingjohn](https://community.weweb.io/u/codingjohn)\
**Post date:** [September 16, 2024, 7:01am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/3 "2024-09-16T07:01:31Z")

</div>

We’re having the same problem right now

---

<div class="post-metadata">

**Author:** ![liweihan](https://avatars.discourse-cdn.com/v4/letter/l/a6a055/32.png) [@liweihan](https://community.weweb.io/u/liweihan)\
**Post date:** [September 16, 2024, 7:11am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/5 "2024-09-16T07:11:42Z")

</div>

On supabse side I got this:

{“auth\_event”:{“action”:“user\_recovery\_requested”,“actor\_id”:“3cdbcc91-4892-421b-be37-956886476768”,“actor\_username”:“—”,“actor\_via\_sso”:false,“log\_type”:“user”},“component”:“api”,“error”:“tls: **failed to verify certificate: x509: certificate has expired or is not yet valid** : current time 2024-09-16T07:00:29Z is after 2024-09-15T23:59:59Z”,“level”:“error”,“method”:“POST”,“msg”:“500: Error sending recovery email”,“path”:“/recover”,“referer”:“( private domain )”,“remote\_addr”:“----”,“request\_id”:“8c3efad461b06459-SJC”,“time”:“2024-09-16T07:00:29Z”}

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 16, 2024, 7:16am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/6 "2024-09-16T07:16:52Z")

</div>

> [@liweihan](#):
>
> Error sending recovery email

Are you using a Custom SMTP?

---

<div class="post-metadata">

**Author:** ![liweihan](https://avatars.discourse-cdn.com/v4/letter/l/a6a055/32.png) [@liweihan](https://community.weweb.io/u/liweihan)\
**Post date:** [September 16, 2024, 7:17am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/7 "2024-09-16T07:17:14Z")

</div>

Yes

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 16, 2024, 7:19am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/8 "2024-09-16T07:19:42Z")

</div>

Maybe there is an issue with that (a certificate?). I’ve found some google links that talk about this.

---

<div class="post-metadata">

**Author:** ![liweihan](https://avatars.discourse-cdn.com/v4/letter/l/a6a055/32.png) [@liweihan](https://community.weweb.io/u/liweihan)\
**Post date:** [September 16, 2024, 7:21am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/9 "2024-09-16T07:21:48Z")

</div>

Yes I think this is Supabase, Im waiting for their response.

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [September 16, 2024, 7:23am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/10 "2024-09-16T07:23:07Z")

</div>

Found this one pretty similar to yours and fairly new  
[https://www.reddit.com/r/Supabase/comments/1c5hnaz/issue\_with\_supabase\_authentication\_failed\_to\_send/](https://www.reddit.com/r/Supabase/comments/1c5hnaz/issue_with_supabase_authentication_failed_to_send/)

---

<div class="post-metadata">

**Author:** ![liweihan](https://avatars.discourse-cdn.com/v4/letter/l/a6a055/32.png) [@liweihan](https://community.weweb.io/u/liweihan)\
**Post date:** [September 16, 2024, 10:02am UTC](https://community.weweb.io/t/error-500-on-supabase-forgot-password/12613/11 "2024-09-16T10:02:30Z")

</div>

This is resolved, caused by postmark SSL cert