Chrome: Bypass NET::ERR_CERT_INVALID for development

Dejan Blazeski
Oct 9, 2019 · 2 min read
Image from google, the error is the same though

So you’ve set your local development, the website uses https which you haven’t added to your approved certs.

You open up the site in Chrome (ie. https://develop.localdev) and chrome welcomes you with:

Your connection is not private
Attackers might be trying to steal your information from develop.localdev (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_INVALID
develop.localdev normally uses encryption to protect your information. When Google Chrome tried to connect to develop.localdev this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be develop.localdev, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Google Chrome stopped the connection before any data was exchanged.You cannot visit develop.localdev right now because the website sent scrambled credentials that Google Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.

A quick way to bypass this message — open Advanced and see if you have a “proceed to website” option.

If not, you can try typing “badidea” or “thisisunsafe” directly in chrome on the same page. Don’t do this unless the site is one you trust or develop. The text “badidea” and “thisisunsafe” says a lot!

Dejan Blazeski

Written by

Founder binge.app. Curious dev. Laravel / Angular / VueJs / React Native / Docker. Love stand up shows.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade