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.

Damselfly

What HTTPS server are you running? – Spotweld

I am using IBM HTTP Server. And this is used in a websphere commerce localhost environment – Damselfly

This issue might be related: #2539223 – Toy

Answer 1

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.

Sonnysonobuoy

Why is it temporary ? what to do for it to stay? – Cadel

Chrome is about to become a secondary browser for me! :/ But thanks for the fix! <3 – Vachil

Answer 2

Instead of

localhost:8000

Write

http://localhost:8000/

Note: replace 8000 with your port number

Socialize

Answer 3

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

Landlubber

Answer 4

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

Forseti

Clearing the cache of my browser worked for me. I am able to resolve the above error by clearing the cache. – Yuhas

Alternatively, you can open a Chrome session in incognito mode. shortkeys: [Ctrl + Shift + N] – Pendentive

Answer 5

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

Friendship

For .NET Core, this was down the bottom in the debug tab when you go to the project properties. – Seaton

Answer 6

Changing https to http worked for me.

Mendicity

Answer 7

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.

Burp

Answer 8

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

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

Potbellied

Answer 9

Instead of

localhost:8000

Replace

127.0.0.1:8000

you try to use the local port number

Mournful

Answer 10

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

Grandeur

Answer 11

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

Whoso

Answer 12

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

Estrellaestrellita

Answer 13

change 'https' to 'http'. It worked for me.

Shostakovich

Answer 14

If you are using vite just add:

import basicSsl from '@vitejs/plugin-basic-ssl'

export default {
  plugins: [basicSsl()]
}

inside the vite.config.js file

This will show the warning Not safe HTTPS

Source on github

Aggrandize

Answer 15

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);
    };
};

Mame

Answer 16

This solution worked for me.

Adding fake parameter to query string fixes the problem.
e.g. http://localhost:3000/?fake=true

Sawmill

Answer 17

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

works to me

Avestan

You should not just ask to turn off the HTTPS. – Hesler