SDK version: @web3auth/modal@^10.1.0.
One of our users is running into a 403 CloudFront error when trying to log in. He’s also shared a screenshot of the issue. This seems to be affecting only him.
Thanks for sharing the details and screenshots! Here’s a summary of your issue for the support team:
Issue Summary:
- Error: 403 CloudFront error when trying to log in via Web3Auth (affecting one user).
- SDK: @web3auth/modal (Plug n Play)
- SDK Version: ^10.1.0
- Platform: Not explicitly mentioned, but likely web (React) based on context.
- Screenshots Provided: Yes (shows 403 error details).
What we know:
- Only one user is affected; others can log in successfully.
- The error is a 403 from AWS CloudFront, which usually means a permission, IP, or access issue at the CDN layer.
Next Steps & Suggestions:
-
Check Client ID and Network:
- Ensure you are using a valid Web3Auth Client ID and the correct network (SAPPHIRE_MAINNET for production).
- Reference: Web3Auth Integration Checklist
-
User-Specific Issues:
- Since only one user is affected, it could be:
- A network/IP block (CloudFront sometimes blocks certain IPs).
- An issue with browser extensions, VPN, or ad-blockers on the user’s device.
- A corrupted browser cache/cookies.
- Since only one user is affected, it could be:
-
Troubleshooting Steps for the User:
- Try logging in from a different network (e.g., mobile data).
- Disable VPNs, ad-blockers, or privacy extensions.
- Clear browser cache/cookies or try a different browser/device.
-
Gather More Info (if needed):
- If possible, please ask the affected user to provide:
- Browser console logs/screenshots when the error occurs.
- The exact time and timezone when the issue happened (helps with log tracing).
- Their public IP address (can be checked at https://whatismyipaddress.com/).
- If possible, please ask the affected user to provide:
Additional Resources:
If you can share the Web3Auth initialization and login code snippet, or any additional logs from the user’s browser console, that would be helpful for deeper investigation.
Let us know if the above steps help or if you have more details to share!
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
Please escalate this issue ASAP. It clearly looks like a problem on your end.