Thanks — I’m on it. This looks like an authentication/login error (not a feature question). Two quick asks so we can triage or escalate fast:
Please share: 1) the Web3Auth / Embedded Wallet SDK version you’re using, and 2) the exact console error text (copy/paste) or the full stack trace (the screenshot alone often misses details). If possible attach the init/connect code (the Web3Auth initialization and where you call connect()).
Quick checks you can try now (most common causes):
- Verify NEXT_PUBLIC_WEB3AUTH_CLIENT_ID in your deployed env matches the Web3Auth dashboard client ID.
- Confirm your allowed origins / redirect URIs in the Web3Auth dashboard include your current domain (including preview URLs).
- Clear localStorage + cookies / try Incognito and a different browser to rule out session/storage or extension blockage.
- Ensure you’re awaiting web3auth.initModal() (or init()) before calling connect(), and that there’s no SSR race in Next.js.
- Check package versions (no inadvertent upgrades). Pin @web3auth/* versions and reinstall if needed.
- Look for network/CSP errors (Failed to fetch, blocked by CSP, or popup blocked). Allow https://.web3auth.io and https://.tor.us if you added CSP headers.
If after the above you still see failures, paste the SDK version, the exact console error, and the init/connect snippet here — I’ll escalate to the team and we’ll investigate further.
Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our monthly Office Hours to discuss this with our engineering team. MetaMask Developer Office Hours