![Localhost Localhost](/uploads/1/2/5/4/125427098/401667378.png)
Jump to Disable Chrome Checking SSL Certificates - Allow insecure connections on localhost in Chrome. Disable Chrome Checking All SSL Certificates. I'm using ASP.NET Core 2.1 which makes local SSL super easy. However, if I hit I may see an error: That's because this is an untrusted SSL cert that was generated locally: There's a dotnet global tool built into.NET Core 2.1 to help with certs at dev time, called 'dev-certs.'
10 April,2018 Jason ParmsDo you use Google Chrome to browse the web? That’s great! Most other internet users are pleased with its smooth user interface.
However, sometimes you might’ve run into an SSL security error “This site can’t provide a secure connection – ERRSSLPROTOCOLERROR” when browsing SSL secure websites on Google Chrome browser.Now, often this error disappears itself when you refresh the page, but sometimes it comes again and again. If you are experiencing such kind of warnings, here we’re explaining various solutions to fix “ERRSSLPROTOCOLERROR”. Check the Date of Your SystemDate is the most common reason behind SSL errors.
![Ssl Ssl](/uploads/1/2/5/4/125427098/691069107.jpg)
When the date of your computer is not in sync with the date of the server that you’re trying to access you’ll face the problem of ERRSSLPROTOCOLERROR on your Chrome browser. The way to fix this is easy – just adjust the date of your system to current date and then try opening the site. You won’t face any problem. Clear Browsing DataSometimes browsing data may also come in the way of your internet surfing experience, thus giving you that nasty SSL error again and again. If the date on your computer is right, follow the steps given below to delete browsing data from your Chrome browser:.
Launch Chrome;. Press Ctrl + Shift + Delete;. Ensure that the time range is set to “All Time”;. Check the checkbox for “Cookies and other site data”;. Check the checkbox for “Cached images and files”;. Hit Clear DataWait for it to complete, and once it has been done try loading the website again in your browser. There’s a very good chance that it will open just fine.
Clear Your SSL StateIf your problem still persists, the next thing you should try is clearing the SSL state of your computer. Follow the steps given below to do that:. Click on the 3 dots showing next to the address bar in Chrome, right below the close button of the browser. Click Settings and scroll all the way down to Advanced Click on the button to expand Advanced settings;. Now scroll down to “Open Proxy Settings” option under System section and click on it;. A window named “Internet Properties” will open.
Go to Content tab in that window and click on Clear SSL StateNow try opening the website once again in Chrome. Disable QUIC Protocol of ChromeStill no luck? Okay, then try disabling the QUIC Protocol of Google Chrome browser. Follow the steps given below to do that:. Paste chrome://flags/#enable-quic in the address bar of your Chrome browser and hit Enter;. Under Experimental QUIC Protocol option, you’ll see that it’s set to “ Default”.
Disable it.Now relaunch Chrome and try opening the website again. Check Your Antivirus SettingsSometimes your antivirus may also be the culprit behind an SSL error. All modern antivirus programs scan the websites for malicious elements and other security threats, which also includes checking the SSL/TLS version of a site.
If a website is using an outdated version of SSL, the antivirus blocks it and doesn’t allow us to visit it. In this case, the problem can be solved by disabling the antivirus temporarily. Just turn off your antivirus for a while and see if you can open the error generating website or not. Check Your FirewallIf a website is present in the blocklist of your Internet Firewall, Chrome will obviously not be able to open it. Check your Firewall to ensure that the website you’re trying to visit is not present in its blocklist. If you find it there, remove it and try loading the website again.
Disable ExtensionsExtensions help in improving the functionality of Chrome significantly, but sometimes they also spoil the internet experience by generating unnecessary errors. Disable your Chrome extensions one by one and open the error generating website again and again as you do that. If you find any extension to be the culprit, remove it. Adjust Your Internet Security and Privacy LevelIf everything mentioned above fails, the last thing that you should try is checking the level of your Internet Security and Privacy because a privacy level too high may also be blocking your access to certain websites.
Follow the steps given below:. Type “Internet Options” in the search bar of your computer and hit Enter;. The “Internet Properties” dialogue box will open. Inside it navigate to Security tab and look at the slider given there. If that slider is too high on the scale, bring it in the middle (to Medium level) and click OK.Now try opening the website that you were trying to open.Out of above-given methods at least one will certainly solve your problem of ERRSSLPROTOCOLERROR on Google Chrome.
Try out each of them until you find your solution.Related Articles:.
App Details:Postman for ChromeVersion 4.11.1win / x86-64Chrome 58.0.3029.110 Issue Report:I am unable to get access to apps running on https locally with visual studio 2017 and iis express 10.0I have reproduced the problem on other machines.The problem is not seen on remote servers only localhost.From chrome.From postman.Postman can't seem to find localhost when SSL is enabled, but chrome can.I thought it might be a cert issue so I added the cert for my iis express (dev server) running on the local machine to the trusted root cert authorities section in the cert store but no luck. I have done some further testing on it, for the app in question when launched from visual studio and run on IIS Express locally when SSL is enabled it actually hosts the apps on 2 ports, one is a standard non SSL based port.I can't get postman to talk to either of these ports for the given app and there doesn't seem to be any logic as to why it works on some apps vs others.What's even stranger is that the apps are all sub parts of a single website in IIS Express and it can't contact the root but it can contact 'some' of it's children. Ok did some digging (after yet another postman reinstall.I opened up the postman dev tools and console to see if I could figure out more about what was going on.First up I get this error in the console.So I took a look in my certs list under settings and found this.Straight up weird, no idea how to solve that.After that I was getting this.Turns out that space after token was actually a newline char (odd that postman didn't trim that as it's never valid to have newline in all the headers i've come across so far (is this ever valid?). That said the 'bulk edit option' should take newline to mean 'ok new header'.Having removed that odd char I came across this error.Which I assume is related to the first error and thus the root of my problem.So.As Postman seems to not have access to a cert that it should be getting from the server.I thought I would try another approach.I took my 'cer' file (that I had to extract using firefox as I couldn't find any option in either chrome or postman to extract this). And dropped it in to a new folder in the root of my hard drive.I granted 'everyone' full control rights to the directory, and then added the cert to postman.So I now have. Still no luck. Every new request is met with.
Where do I go from here? I found that after doing all of the above I rebooted my machine and some versions of postman are happy others aren't. It seems to come and go with each new update to postman.I also think that windows does some weird profile loading of cert stores so any time you add or remove a cert fro mthe 'personal' store on the machine, reboot just in case.With all this in mind I got to a point where I basically just built a 'postman like' UI on a web page and now I just use that. It works, flawlessly, every time.No idea why postman can't just be the same. It's a dev / testing tool after all, it shouldn't care if something is secure unless you tell it 'be uber strict as that is the test i'm trying to perform'.good luck though! I'm condensing this discussion and adding our thoughts here.The original is related to working with untrusted SSL certificates in Postman for Chrome. Postman for Chrome apps rely on Chrome to send and receive requests and Postman app has no control over SSL certificate verification performed by Chrome as part of sending the request.
Chrome will honor untrusted certificates you have added to your OS as trusted (hence behavior) and there is also a way to whitelist certificates on a case to case basis by opening the link in Chrome and clicking 'proceed' in at the 'Your connection is not secure' (which is why you are seeing behavior). Since you seem to be working with IIS Express and VS, which I believe generates self-signed certificates on demand, you are required to do these steps again and again to keep your API working with Postman for Chrome.Having said this, we completely agree with your sentiment that Postman is a testing tool and should not be strict about SSL verification, which is why we have exposed SSL cerificate verification in our native apps - to completely turn off SSL verification.
(this is not available in Postman for Chrome as we have no control over SSL verification in Chrome apps).Note: There seem to be some confusion regarding Client Certificates. These are client certificates that Postman sends to your server and does not affect the server certificate verification behavior.Do let us know if we have missed anything and if you are still facing issues with SSL verification in our native apps after you have turned the setting off. I totally forgot about this issue then.After a while i ended up with a broken install of windows on my home machine (you know 'reasons', windows update, ect). That led me to get some more insight on this problem which I logged in ticketI've come to the conclusion that postman does support this scenario, it just doesn't want to by default like somehow a local dev environment is a sub standard service because I didn't go to the effort of signing my IIS express instance with a cert from say. Go daddy (go figure. Right?).I really love that postman is trying to push standards.That said, I genuinely think that this scenario is crazy simple and a norm for many.Postman should have some sort of exception to just 'behave like chrome' and report that the cert is not valid but still talk to the API and return a response regardless.Maybe have a means to 'turn ON strict mode' which then gets this aggressive instead of enforcing it by default would be better (reccommendation)?Kudos to the Postman team though for getting involved and actively trying to understand the frustration here, it's much appreciated!
I get where you're coming from. Unfortunately I can't agree to this solutionThere's nothing I haven't tried since morning.I am adding client certificate authentification to the project that I wrote with asp.net core. My application is running and the client is waiting. I'm sending a request via Postman to the application running in local. I've added the certificate to the exact specifications and tried all possible combinations. (subject localhost etc that numaan defined) I log the result via both fiddler and postman console. I even observe it with visual studio output.
I observe that both the fiddler and the postman console, the certificate cannot be sent or even the postman is not aware of its existence. But someone writing about a solution (like this). Can it be corrupted? Fiddler is a proxy, that will only make the situation more complex and likely cause you more issues. I use to use it a long time ago but dropped it when it started causing more problems than it solved.I'm logging information on the server (my web app) and on the client (browser / postman console) running on the same machine, the UI above was just something I threw together to show difference between postman and chrome when handling self signed certs.It sounds like you're talking about client certs though.The issue here is postman's lack of trust of server certs signed by the server and not a trusted authority. Client certs are a different scenario but loosely related I would think.We are purely talking about localhost trust for simple debugging scenarios, SSL still works the way it works in all cases.