I have successfully implemented web3auth in my web application in a jwt flow. When used on localhost it is flawless. Now when deployed on my website, I consistently get that error:
WalletLoginError: Failed to connect with wallet. Failed to login with openlogin
I have no more clue about it. What should I do? How could I investigate?
Hello, @oauth.
To provide you with better assistance, would you be able to share additional information such as screenshots or code snippets? This will allow us to understand the issue more clearly and provide more effective solutions. Thank you.
Sure, again everything works with every social logins on localhost, they all successfully trigger the web3auth popup and my code can continue through the rest of the app with the web3auth address, I use the wagmi connector for that. But on the deployed URL, although it works with different authentication means (like jwt after an OTP code verification), social fails with this error
Error while connecting WalletLoginError: Failed to connect with wallet. Failed to login with openlogin
at eA.fromCode (723-ce0c5f24da2db512.js:8:14585)
at eA.connectionError (723-ce0c5f24da2db512.js:8:14720)
at es.connect (723-ce0c5f24da2db512.js:8:35887)
at async es.connectTo (723-ce0c5f24da2db512.js:8:28825)
at async eo.connect (723-ce0c5f24da2db512.js:9:235814)
at async j (_app-97b1eecb2a4a2f98.js:362:6685)
connect
await in connect
This seems to come from the “connectTo” method which is used to init web3auth. But since I use the wagmi connector, I don’t call the function in my code. As can be seen below, when I get a jwt from a successful authentication in next-auth, I connect wagmi with the web3auth connector.
Ah stupid problem, popups were blocked from my deployment URL… Would help to have a better error message.
Yes it is solved thank you very much
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.