Hi thanks for your question could you please reference this past post: Web3auth on localhost not working after migration - #2 by system
And indeed localhost is intentionally blocked on Web3Auth Sapphire Mainnet for security reasons and cannot be allowlisted. Local development is supposed to use Sapphire Devnet.
If your Unity WebGL build can still log in from localhost, likely explanations are:
- It’s actually using a Devnet client ID.
- The login flow you’re using isn’t hitting origin validation in the way you expect.
- The app isn’t truly being served from
localhost(e.g. tunnel/proxy). - An existing Web3Auth session is being restored.
The first thing I’d check is the runtime values for clientId, web3AuthNetwork, and window.location.origin