Web3 Auth Failing

Report Outage
1

When creating a brand new account on devnet, web3auth is failing for CORS and epoch errors.

The login is working fine with existing accounts.

web3auth_1
web3auth_11036×856 169 KB

web3auth_2
web3auth_21016×206 36.2 KB

web3auth_3
web3auth_31588×922 36.1 KB

2

Hi Charles, thanks for sharing the details and screenshots!

From your description and the images, it looks like you’re encountering CORS and epoch errors specifically when creating new accounts with Web3Auth, while logins for existing accounts work fine.

Here’s a summary of what we know so far:

Issue Summary:

  • Problem: CORS and epoch errors when creating new accounts (existing accounts work).
  • SDK/Platform: Not specified (please confirm if you’re using Web3Auth Plug and Play, Core Kit, or another SDK, and on which platform—Web, React, etc.).
  • Screenshots: Error messages indicate CORS issues and possibly a problem with time synchronization (epoch error).
  • Context: You referenced documentation about different wallet addresses due to verifiers, client IDs, environments, or product differences, but your main issue seems to be a technical error during new account creation.

Next Steps / Information Needed:
To help you further, could you please provide:

  1. SDK & Platform Details: Which Web3Auth SDK are you using (e.g., Web, React, Plug and Play, Core Kit)? What version?
  2. Initialization & Login Code: Can you share the relevant code snippets for how you initialize and call login for Web3Auth?
  3. Verifier Details: Are you using a custom verifier or aggregate verifier? If so, what’s the verifier name and login method?
  4. Console Output: If possible, please attach a screenshot of your browser console showing the full error stack for the CORS and epoch errors.

Potential Causes & Solutions:

  • CORS Errors: These often occur if your frontend is making requests to a backend or third-party endpoint that doesn’t allow your domain. Double-check your allowed origins in both your Web3Auth dashboard and any custom backend you may be using.
  • Epoch Errors: These can occur if the client and server clocks are out of sync, or if there’s an issue with the JWT token’s validity period. Make sure your device’s time is correct and that your authentication flow isn’t reusing expired tokens.
  • Verifier/Client ID Issues: If you recently updated your verifier or client ID, ensure all SDKs and environments are using the correct, matching values. See Web3Auth Docs: Different Private Keys/Wallet Address.

Reference Docs:

Once you provide the above details, we can help you pinpoint the cause and resolve the issue quickly! Thank you for your patience.

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

We are experimenting the same issue. Is there any known problem affecting devnet?

4

Not related to CORS, but we are also having issues with DEVNET + custom auth.

Seems like share retrieval is failing. No issues on MAINNET

5

@here Please try once again, we had some disruption on the sapphire_devnet network, all is good on the sapphire_mainnet. Apologies for the disruption.
Please use sapphire_mainnet for production environment.