Don't try to find the source of the problem."
Oh, and hey, you should try it too, if you ever get the same invalid SSL certificate as me, because obviously, making the warning message go away is the right way to fix this issue. I don't know who or why, but here's how I'll just bypass all the warnings I should receive, and browse in the most insecure way possible. "Oh, someone/something down the line between me and some secure website is replacing the site's real SSL certificate with his own. This must be the worst possible hint ever! I guess this problems only exist in rare circumstances with some proxy servers between your computer and the Internet. Maybe not many people will need this hint. I wouldn't do online banking this way there I would be encouraged when Chrome tells me that there's something wrong with the site. That will open Chrome as usual but lets you browse any HTTPS site that has a problematic certificate and was blocked before. Applications/Google Chrome.app/Contents/MacOS/Google Chrome -ignore-certificate-errors &> /dev/null That's not very comfortable but it works (last tested with Chrome 34).Īssuming Google Chrome is in your Applications folder, go to the Terminal and type following command: But you can start Chrome with the flag -ignore-certificate-errors.
Unfortunately there's neither a visible setting to set Chrome to warn me but allow the warning to be ignored, nor is that one in about:flags. For example this problem appears when I try to access my router at home or some other sites having problematic certificates - but they play fine when I'm at home.įinally I found a solution for the problem. Safari just shows a blank page and I'm not able to open that specific web site although I'm sure that this site is not going to harm my computer or myself. There's something with Chrome (and Firefox as well) that has driven me crazy for some years: when browsing the web via a proxy server while at work I can't access some pages via the HTTPS-protocol.Ĭhrome and Firefox are showing error messages like this one and this one (sorry, both are in German).
0 kommentar(er)
