This topic was originally posted by joseph1 on 8/27/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.
From Chrome browser (version: Version 139.0.7258.154 (Official Build) (arm64)), on a desktop, when I attempt to login to web3auth.io by Signing-in via my Google account (clicking on the Continue with Google button), I am unable to be authenticated successfully. Once I sign-in with Google, the popup modal just remains open. My browser log shows the following error:
Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML
Thank you for providing detailed information about the issue you’re facing with logging into Web3Auth via Google on Chrome. Here’s a summary of your report for the support team:
Issue Summary
SDK Details: Web3Auth Plug and Play (PnP), React SDK
Platform: Chrome browser (Version 139.0.7258.154, arm64) on desktop
Login Method: Google (social login)
Issue: After clicking “Continue with Google,” the popup modal remains open and authentication does not complete.
Browser Console Error:
Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML
Code/Setup: Using the recommended setup for Web3AuthProvider and configuration from the docs.
Next Steps / Troubleshooting
The error suggests a possible issue with how a JavaScript module is being loaded—often related to bundler configuration or a missing/corrupted file. Here are some suggestions and questions to help the support team diagnose further:
Bundler Configuration: Are you using Vite, Webpack, or another bundler? Sometimes, missing polyfills or misconfigured public paths can cause this error. Please check the Vite, Webpack 5, or other relevant troubleshooting guides.
Network Tab: In your browser’s developer tools, can you check the Network tab to see which script is failing to load and what the actual response is? (e.g., is it a 404 or 500 error, or a redirect to an HTML page?)
Code Snippet: If possible, please share the code snippet where you initialize and render the <Web3AuthProvider> and any relevant configuration (excluding sensitive data like your clientId).
Reproducibility: Does this issue occur in other browsers or only on this Chrome version?
Console Screenshot: If you can, please attach a screenshot of the full console error and the failing network request.
Double-check that all dependencies are installed and up-to-date.
Ensure your bundler is correctly configured to serve JavaScript modules (especially if using Vite or Webpack 5).
Clear your browser cache and try again.
If you can provide the initialization code and a screenshot of the failing network request, that will help the support team assist you faster. 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
My top guess is that there might be some Chrome extension that might be interfering with the redirecting back process.
Can you try disabling some of them and try again?
Content from Web3Auth Community