Chrome://flags/#allow-insecure-localhost May 2026

If you’ve ever tried to test a service worker, a geolocation API, or any "secure context" feature on a local development server, you’ve likely run into this error: "The page you are trying to access is not secure (HTTPS)." You know your code is safe. It’s running on localhost:3000 . But Chrome refuses to play ball, blocking features because the page isn’t served over HTTPS.

Happy coding — securely, except when you’re not. 😉 Have you ever used this flag for something unexpected? Share your story in the comments! chrome://flags/#allow-insecure-localhost

Just remember to when you’re done testing, or at least be aware it’s active. If you’ve ever tried to test a service