New device detected [Bless]

Help - Plug n Play
1

Hi I am trying to login to bless network and they are using web2auth.

Now the problem is over the time the chrome version got updated and due to that it thinks that is new device. I do not have recovery phrase or password to login. So please help me to login.

I guess most likely solution would be to have recovery phrase but this issue will be quite common due to chrome version upgrade

image

2

Thank you for sharing your issue, Vivek. Here’s a summary of your situation for the support team:

Issue Summary

  • User Goal: Access their account on Bless Network (which uses Web3Auth Plug n Play / Web2Auth).
  • Problem: After a Chrome browser update, Web3Auth is detecting the login as a new device. The user does not have a recovery phrase or password and is unable to log in.
  • SDK/Platform: Plug n Play (PnP) / Web2Auth, likely on web (Chrome browser).
  • Error/Message: “New device detected” (Bless Network).
  • Recovery Options: User has not set up a recovery phrase, backup factor, or MFA previously.
  • User Concern: This issue may be common with browser/device changes, and the user is seeking a way to regain access.

Context & Technical Details

  • Web3Auth (especially with Plug n Play and MPC-based flows) uses device factors and backup factors for account recovery.
  • If you lose access to your device (or browser storage is cleared/changed), you typically need a backup factor (recovery phrase, email, OTP, etc.) to regain access.
  • Without a backup factor or MFA, recovery is not possible due to the non-custodial, secure design.

References:

Next Steps / Recommendations

  1. If you have access to any backup factor (recovery phrase, backup device, or enabled MFA), please use it to recover your account.
  2. If you do not have any backup factor set up, unfortunately, due to Web3Auth’s security model, there is no way to recover access. This is by design to ensure the highest level of security and user control.
  3. For future use: Always set up a backup factor (such as a recovery phrase or social recovery) when prompted during onboarding. This will help prevent loss of access if your device/browser changes.

For the Support Team:

  • The user is locked out due to device factor loss (browser update).
  • No backup factor or MFA was set up.
  • Using Plug n Play (Web2Auth) on Chrome for Bless Network.

If you have any backup factor or recovery method set up, please try those. If not, unfortunately, account recovery is not possible. For more details, see the Web3Auth Recovery FAQ.

If you have any other questions or need help with setting up recovery in the future, let us know!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours

3

Hey @viveksharmainfosys

Just to clarify — Web3Auth is a self-custodial system, so it never locks you out on its own. If you’re seeing that recovery screen, it’s almost always because your browser/device changed or the local cookies were lost (due to a browser update, using incognito, or manually clearing storage).

When you first set up MFA, you may have entered a different email for receiving your recovery phrase, please check that inbox (including the spam folder). If you still have your recovery password from the MFA setup, that can be used as well.

This design is intentional ,it’s there to protect your account in case your main login method is compromised. Web3Auth itself does not store or have access to your recovery password or phrase, so if both factors are lost, there is no way to restore them, similar to how Gmail can’t recover your account if you lose access to both your password and all backup options.

4