localhost blocked on Chrome with "Privacy Error"
Solution 1
Try this:
In Chrome, put in chrome://flags/#allow-insecure-localhost in the address bar.
Enable the option that says "Allow invalid certificates for resources loaded from localhost".
Restart Chrome, and it should allow the site.
Solution 2
From Chrome version 63, it will redirect all .dev extension to domain https So try another extension to another, ex .test, .local... You can refer here: https://docs.serverpress.com/article/234-your-connection-is-not-private-google-chrome
Solution 3
Try typing in your are blocked page thisisunsafe. Simple type this word on keyboard. I found solution from this https://medium.com/@dblazeski/chrome-bypass-net-err-cert-invalid-for-development-daefae43eb12
Solution 4
It worked for me just by changing " .dev" to ".local" I'm using windows 10
Solution 5
your connection is not private for virtual host in XAMPP
I've faced the same problem, Now It has been solved it.
don't use '.dev' for your local domains - the new chrome (version 63) redirects all .dev -Domains to 'https://name.dev'
Try to rename your local domains to something like '.test' and 'phpmyadmin.test' or whatever
wyboo
Updated on July 09, 2022Comments
-
wyboo almost 2 years
Google Chrome is blocking
localhost
.I'm using
XAMPP
withApache localhost
, ports80
and443
. Google Chrome is up to date.I'm getting the following error:
Your connection is not private
Attackers might be trying to steal your information from localhost (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID
-
Andrew about 7 yearsWould there be any downsides to this? Any actual issues with allowing insecure from localhost?
-
Kyle Erickson almost 7 yearsI can't see why, seeing as localhost is just your local machine.
-
DrLightman over 6 yearsNot working for me on Chrome 62.0.3202.94, even if the flag is there it seems to not have any effect.
-
Tom Shaw over 6 yearsWorked for me after changing hostnames from *.dev to *.local. Tested on Apache Windows 10.
-
black_yurizan over 6 years@TomShaw Can confirm, I changed my example.dev to example.io and it started to work
-
Rumit Patel over 6 yearsshould be in comment.
-
Hammad Khan about 6 yearsThis exactly solved my problem. Was using .dev domain, changed that to .git and it worked flawlessly.
-
Nathan about 6 yearsThis was my issue as well, using the .dev domain, changed it to .local and worked fine
-
Christia almost 6 yearsThis solution didn't work for me but the solution below about not using .dev worked! FYI. Try both.