Skip to main content
March 8, 2026
Question

ServerError 500 when attempting recovery

  • March 8, 2026
  • 3 replies
  • 104 views

Failed to complete recovery.

An unexpected error occurred.

  • 500

Error Code: 500

Session: 6F3OMHGWDNBZRM42FDGTRQ225U

Time: 2026-03-08T17:02:26.250Z

3 replies

March 9, 2026

Hello, we have recently begun to notice a significant number of errors in our employees' login attempts, always in scenarios where they have been configured to log in via Microsoft EntraID SSO. The errors vary, even after clearing the cache, deleting the extension, or using another browser.

Even though the recovery process has started, the user is unable to proceed with the recovery.

 

We have had the application for some time and have never encountered the current problems. We request your assistance in resolving this issue.

1P_Dave
1Password Employee
March 9, 2026

Hello @tiago_bt and @edeak54! 👋

I'm sorry that you're both running into issues where attempting to recover a team member results in a ServerError 500 message. Our development team is currently investigating this issue and we hope to have more news to share soon. 

Once a fix is ready, or there are any updates to share, I'll update this thread. 

-Dave

1P_Dave
1Password Employee
March 9, 2026

@edeak54 and @edeak54 

Thank you for your patience. Our team has released a fix that addresses an issue that may have caused a ServerError 500 when recovery users, please try to complete recovery again. 

If you're still seeing the same error message then please send an email to support@1Password.com and include the following:

  • Save a console log in your browser
  • A link to this thread: 

    https://www.1password.community/discussions/1password-work/servererror-500-when-attempting-recovery/168253

  • You username: username


After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like
[#ABC-12345-678]. Post that here, and I'll be able to locate your message and make sure it's gotten to the right place.

-Dave