Tea protocol authweb3

Web3Auth Community General
1

help me to login , i never set 2fa for tea protocol ,but now i open your web3 ask me for verified. and my recovery phrase showing wrong. please help me’
‘’‘’

1 Like
2

Hello A. Ansari!

It sounds like you’re encountering an issue with logging in where you’re being asked for verification, and your recovery phrase isn’t working. To help you more effectively, could you provide a bit more information? Specifically:

  1. Are you using Web3Auth’s social login or a different way to authenticate?
  2. Could you share the specific error message or a screenshot? This could include what’s being shown when your recovery phrase is said to be wrong.

It would also be helpful to know:

  • Any login methods you’ve tried (e.g., Google, Facebook)
  • If there’s a particular SDK or platform you’re implementing this on

Once we have more details, the support team can assist you better. In the meantime, you might also want to check the Web3Auth troubleshooting guide for any immediate assistance. Thank you!

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 @aansari.aa143,

If you’re seeing the Recovery Password option on the MFA screen, that means you had set it earlier — it’s only shown if it was configured. So if you’re being asked for it now, you’ll need to enter that exact password to regain access.

However, if you’re not seeing the Recovery Password option at all, it likely means your account was created before TEA Protocol enabled that feature, and you never got a chance to set it up.

Also, if you found a recovery phrase in your mailbox, please note — we never send the recovery phrase to the same email as the social login, as that defeats the purpose of MFA. If you received a phrase in the same inbox, it’s most likely from another dapp that also uses Web3Auth. Avoid using that, as it won’t work here.

Unfortunately, since Web3Auth is a non-custodial solution, we don’t store or reset recovery credentials.

4