ERR_SSL_PROTOCOL_ERROR not able to see https localhost pages in chrome browser

Question

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.

I am using IBM HTTP Server. And this is used in a websphere commerce localhost environment — jikku, Jan 09 '18 at 04:14
This issue might be related: https://stackoverflow.com/questions/2538723/ssl-received-a-record-that-exceeded-the-maximum-permissible-length-error-code — Victor S, Sep 27 '19 at 15:08

score 27 · Answer 1 · answered Feb 18 '22 at 19:24

27

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.

answered Feb 18 '22 at 19:24

Mehmet

456
4
5

Why is it temporary ? what to do for it to stay? – Ohad Bitton Sep 07 '22 at 12:42
Chrome is about to become a secondary browser for me! :/ But thanks for the fix! <3 – Egil Hansen Jun 02 '23 at 16:03

score 18 · Answer 2 · answered Jul 14 '20 at 15:29

18

Instead of

localhost:8000

Write

http://localhost:8000/

Note: replace 8000 with your port number

answered Jul 14 '20 at 15:29

Gabriel Arghire

1,992
1
21
34

score 12 · Answer 3 · answered Feb 01 '22 at 21:56

12

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

answered Feb 01 '22 at 21:56

mattyb

1,011
2
10
26

score 11 · Answer 4 · answered May 29 '19 at 22:52

11

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

answered May 29 '19 at 22:52

tomstan11

1,047
7
9

1

Clearing the cache of my browser worked for me. I am able to resolve the above error by clearing the cache. – DaminiVyas Aug 10 '20 at 09:13
1

Alternatively, you can open a Chrome session in incognito mode. shortkeys: [Ctrl + Shift + N] – TJ Galama Feb 19 '21 at 10:47

score 7 · Answer 5 · answered Sep 25 '18 at 21:00

7

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

answered Sep 25 '18 at 21:00

Arun E

71
1
4

For .NET Core, this was down the bottom in the debug tab when you go to the project properties. – David Klempfner Apr 01 '21 at 03:09

score 6 · Answer 6 · answered Nov 20 '20 at 16:13

6

Changing https to http worked for me.

answered Nov 20 '20 at 16:13

vvlnv

394
3
9

score 3 · Answer 7 · answered May 12 '21 at 15:14

3

I cleared Google Cache on Chrome://settings/privacy
Instead of using the 'https://localhost:4200' or 'http://localhost:4200', I just used 'localhost:4200' and that worked well.

answered May 12 '21 at 15:14

Carla Sahagun

31
1

score 2 · Answer 8 · answered Nov 02 '22 at 21:54

2

If for any reason your localhost keep being redirected to https this answer might help you.

Change https to http (But do not hit enter)
Click and hold the reload icon
Choose the 3rd option Empty Cache and Hard Reload

answered Nov 02 '22 at 21:54

crg

4,284
2
29
57

score 1 · Answer 9 · answered May 16 '18 at 10:37

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

score 1 · Answer 10 · answered Nov 17 '22 at 11:08

1

Instead of

localhost:8000

Replace

127.0.0.1:8000

you try to use the local port number

answered Nov 17 '22 at 11:08

hsnozacar

11
1

score 0 · Answer 11 · answered Mar 16 '23 at 21:00

0

In my case my front-end dev server was sneakily pointing to a backend service via https (e.g. API_URL=https://localhost:3001)

answered Mar 16 '23 at 21:00

Alex

631
1
8
33

score 0 · Answer 12 · answered Aug 16 '23 at 19:55

0

Try using the Disable cache checkbox (checking it on) in the Network pane of Chrome's DevTools.

answered Aug 16 '23 at 19:55

Lawrence

133
2
6

Luis Lobo · Answer 13 · 2022-03-04T14:49:13.447

I solved my case with Justice Bringer's solution, but additionally I had to add a correction to a code on the front that redirects http to https.

if (window.location.protocol !== '4200') {
     forceHttps();
};

// force-to-https.js v1
function forceToHttps() {
    if (location.protocol == 'http:') {
        var linkHttps = location.href.replace('http', 'https');
        // via location
        window.location.protocol = 'https:';
        window.location.href = linkHttps;
        // via click
        var a = document.createElement('a');
        a.setAttribute('href', linkHttps);
        a.setAttribute('style', 'display: none !important;');
        a.click();
        // reinforce
        setInterval(function() {
            window.location.href = linkHttps;
            a.click();
        }, 3500);
        // via meta
        var meta = document.createElement('meta');
        meta.setAttribute('content', '0;URL=' + linkHttps);
        meta.setAttribute('http-equiv', 'refresh');
        (document.head || document.getElementsByTagName('head')[0]).append(meta);
    };
};

score -3 · Answer 14 · edited May 20 '22 at 15:04

-3

chrome://flags -> https and then set it to enable

works to me

edited May 20 '22 at 15:04

Tyler2P

2,324
26
22
31

answered May 18 '22 at 23:18

Jônatha Mendonça

1
2

You should not just ask to turn off the HTTPS. – Mushfiq Feb 06 '23 at 16:45

ERR_SSL_PROTOCOL_ERROR not able to see https localhost pages in chrome browser

14 Answers14

Linked