Verification Link gives page that says "Error: your email address could not be verified."

We have enabled the force-email-verification rule, and users are sent a verification URL upon first attempting a login. When they click on the URL, they get a page with the following:
Your email address could not be verified.
Despite this, the users have their emails authenticated (i.e., the logs show a successful verification). How do we prevent this misleading error message from appearing?

Hey @troyappel, we found an issue in the flow and fixed it about an hour back. Can you confirm that you are now seeing a success message when verifying the user?

FWIW, the users would have been able to login because the emails were correctly verified when they clicked the link, but the UI just showed an error.

Hi @thameera,

I’m having this issue right now. 100% reproducible on my mail address.

I opened a support ticket.



1 Like

Perfect! Then somebody from our developer support team is already working on that. Once you have it resolved can you share what it was? Thank you!

We are still experiencing same issue. but it occurs occasionally and not always. Is there any work around or resolution for it?


Experiencing the same issue. Any update on a resolution?

Experiencing the same issue. If Auth0 fix this issue, will you notify us?

Hi @konrad.sopala,

We have a user in Germany who received this error message yesterday. All logs show that the verification was successful. But the end-user is confused as to what to do.

Is this being worked on by the Auth0 dev team?

HI folks,

The generic error message here is a known issue. In most cases it seems the verify link has inadvertently been used more than once, but our generic error message doesn’t differentiate between “already verified” and “other error” at the moment–it definitely should do at least that and I know this is frustrating from a user perspective.

There are several open issues related to this, but no ETA for a fix right now. Please chime in here if you’re affected by this and I’ll use the responses to raise visibility internally.




Thanks for the heads-up Matt!

We are seeing this for some but not all users.

1 Like

Hi Matt,

We have experienced the same issue for some of the users as well.

1 Like

Still seeing this, has this been resolved?

1 Like