Most of our users do not have any problem loging in through the google oauth nor the passwordless email login.
However, some of our users are having problem loging in with the passwordless email login and get a « Error - Something went wrong - Could not get result torus nodes ». Strangely that user can get log in using his email (gmail) using the google oauth but not the passwordless email. however, he needs to retrieve his passwordless email wallet since he bought an NFT using it (ETH wallet).
What’s going on ? I tried reproducing his error on my laptop (where I can both login using google oauth & passwordless email on the same address) and the error still happens. it seems like it must be email related (it’s a gmail email, where the passwordless link was opened from a linked outlook.live account).
Any idea what might be going on ?
I’m trying to reply as best as I can to the questions below, but I’m unsure what some of them ask. please let me know if you need anything else.
When asking for help in this category, please make sure to provide the following details:
If the issue is related to Custom Authentication, please include the following information (optional):
Verifier Name:
JWKS Endpoint:
Sample idToken (JWT):
Also, kindly provide the Web3Auth initialization and login code snippet below. This will help us better understand your issue and provide you with the necessary assistance.
Firstly, please provide your Dapp URL to check the behavior from our end. Could you also provide some sample email addresses for Passwordless login which the users are unable to login, to check the logs?
Firefox browser needs some tweaking in it’s settings. I will link the article here for that. I would suggest we use Chrome as a reference browser for troubleshooting here.
We have some latest versions for the below packages which you should consider later:
Thanks for the quick reply Is there a way to MP/email you this information ? I’d rather not leak my client’s email on this public forum and I cannot reproduce the issue with my own emails.
Have you upgraded the package versions to these and checked the result? The error indicates your app is using an older version of Openlogin v5 when the latest is v6
The latest version v7 is packed with essential updates, enhancements, and some pivotal changes to further ease your development process. You can read more here
Our user is still having the same problem with the updated (could not get result from torus nodes). I’m PM’ing you the problematic address in case that can help.
This is happening on MainNet. The user gets this error after completing the verification (when clicking on the button in the confirmation email and coming back to the tab)
PS: I’m sharing with you the implementation code via PM
If Outlook is appending any additional parameters to the verification URL , you would need to check from your side. Also, do check if there are any email settings from Outlook preventing access from completing the verification.