Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

ERR_SSL_PROTOCOL_ERROR not able to see https localhost pages in chrome browser

Not able to see the localhost https page properly in chrome . It says :

**This site can’t provide a secure connection**
localhost sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR

I tried -deleting domain localhost from - chrome://net-internals/#hsts But not helped.

like image 345
jikku Avatar asked Jan 03 '18 11:01

jikku


8 Answers

Try clearing your website data and cache from chrome. Old htaccess files can cause problems on localhost.

like image 96
tomscoding Avatar answered Oct 09 '22 19:10

tomscoding


Instead of

localhost:8000

Write

http://localhost:8000/

Note: replace 8000 with your port number

like image 38
Justice Bringer Avatar answered Oct 09 '22 19:10

Justice Bringer


If you're using Visual Studio

Then go to project properties => enable SSL as True and select the SSL URL with port number Showed as per the properties

like image 30
Arun E Avatar answered Oct 09 '22 17:10

Arun E


Changing https to http worked for me.

like image 29
Vladislav Leonov Avatar answered Oct 09 '22 19:10

Vladislav Leonov


Go to chrome://net-internals in the Chrome and switch to the Domain Security Policy tab.

In the "Delete domain security policies" section at the bottom, write "localhost" in Domain field and press the "Delete" button.

Note, this is a temporary fix.

like image 43
Mehmet Avatar answered Oct 09 '22 19:10

Mehmet


What worked for me was using http://127.0.0.1:3000/ (its DNS entry) instead of http://localhost:3000/

like image 38
mattyb Avatar answered Oct 09 '22 19:10

mattyb


In my case, my antivirus was the culprit. Somehow the site was considered unsafe and it replaced the response with the 'website blocked' page of the antivirus application. This information, however, was not sent with TLS so the browser interpreted that as an ERR_SSL_PROTOCOL_ERROR

like image 21
Klaus Avatar answered Oct 09 '22 18:10

Klaus


  1. I cleared Google Cache on Chrome://settings/privacy
  2. Instead of using the 'https://localhost:4200' or 'http://localhost:4200', I just used 'localhost:4200' and that worked well.
like image 44
Carla Sahagun Avatar answered Oct 09 '22 19:10

Carla Sahagun