Error AtlasError Documentation and Resolution
Back to searchMore Vite errors

Vite

Vite network requests stop loading with a self-signed SSL certificate

Network requests stop loading

Chrome can ignore the cache behavior Vite relies on when the dev server uses a self-signed SSL certificate, which can leave requests stuck reloading.

Network requests stop loadingnetwork

Observed message

Network requests stop loading

Why it happens

  • The Vite dev server is using a self-signed SSL certificate.
  • Chrome is ignoring caching directives because the certificate is not trusted.
  • The browser keeps reloading assets instead of using the normal dev-server cache behavior.

How to fix it

  1. Use a trusted SSL certificate for the Vite development server.
  2. Import the development certificate into the system trust store if you must keep a local certificate.
  3. Retest in a clean browser session after the certificate is trusted so stale reload behavior is cleared.

Official reference

Vite: Troubleshooting

Related errors

TypeError: Failed to fetch dynamically imported moduleVite app failed to fetch a dynamically imported moduleWhite screen without logged errorsVite app shows a white screen because browser extensions are blocking requestsENOENT: no such file or directory / Module not foundVite build failed because of case-sensitive file pathsAccess to script at 'file:///...' from origin 'null' has been blocked by CORS policyVite built file failed because it was opened over the file protocol

Explore more

ViteBrowse more Vite errorsnetworkBrowse more network errors
Vite network requests stop loading: self-signed SSL causes and fixes | Error Atlas