I formatted my PC and when I try to log into BLESS, I get the error message “Failed to login - Please refresh the page. User already exists with different type of login,” and I can’t log in.
Steps I have taken to resolve the issue:
Cleared the cache and restarted the browser
Installed Firefox and tried logging in
Re-formatted the PC
Reset the third-party permissions for my account
Tried logging in with the same email using the email login method instead of Google login (which was the previous method)
Even after trying everything I know, the issue still persists. When I contacted the BLESS support team, they mentioned that it seems to be a problem with the WEB3AUTH permissions.
Can you confirm why this is happening and suggest a solution?
I understand you’re having trouble logging into the BLESS network using Web3Auth and you’re seeing the error message: “Failed to login - Please refresh the page. User already exists with different type of login.” This issue seems to be related to the login method discrepancy.
From your description, here’s what we’ve gathered:
SDK Details: Plug n Play
Platform: It seems to occur across multiple browsers post-PC reformatting
Login methods tried: Google (initial), Email
To help you further, could you provide:
Web3Auth Initialization & Login Code Snippets - This can help us see how the login is being initiated.
Browser Console Screenshots - These can provide insight into any hidden errors.
Meanwhile, here’s a possible solution you can try:
Verify if your email is linked to multiple login methods in the Web3Auth or BLESS platform and try to consolidate or unlink any redundant connections.
Once we have the code snippets and console logs, we can dig deeper into this.
Let us know how it goes!
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
Verify if your email is linked to multiple login methods in the Web3Auth or BLESS platform and try to consolidate or unlink any redundant connections.
→ How do you do this? Do you have a link?
It’s possible that BLESS is using a service that only allows unique logins. In that case, Google login and email passwordless authentication wouldn’t work since both methods share the same email. And you might have use one for signup and using other to login.
Have you reached out to the BLESS network developers regarding this?
I understand your frustration, but making broad statements like this without specific context can be misleading. If you’re experiencing recurring issues across multiple projects using Web3Auth, I’d be happy to help troubleshoot. Could you share more details on the challenges you’re facing? Many teams have successfully integrated Web3Auth without issues, so understanding the specifics might help identify whether this is a configuration-related matter or something else.
Can you please click on the Recovery Phrase option? You’ll find details on where the recovery phrase was originally sent. Try searching your email inbox for the subject “Your Web3Auth backup phrase”.
If you’re unable to find the email, unfortunately, as a non-custodial solution provider, we do not store or reset MFA credentials. There is no way to recover the account without the backup phrase. Let us know if you have any other questions.
Thank you for your feedback. But we cannot help you in restoring access to your account as we do not store your backup phrase. It’s only and only in your custody. Losing it means losing the account. The mail, if not present, might have been deleted.
Thanks for reaching out.
