I’ve been using Google Chrome as my primary browser for the last few years. Sorry, Firefox, but with all the stuff I need to work installed, it’s to slow and almost unusable.
Let’s say you have a server with a self-signed HTTP SSL certificate. Every time you hit a page, you get a nasty error message. You ignore it once and it’s fine for that browsing session. But when you restart, it’s back. Unlike Firefox, there’s no easy way to say “yes, I know what I’m doing, ignore this.” This is an oversight I wish Chrome would correct, but until they do, we have to hack our way around it.
Caveat: these instructions are written for Mac OS X. PC instructions will be slightly different at PCs don’t have a keychain, and Google Chrome (unlike Firefox) uses the system keychain.
So here’s how to get Google Chrome to play nicely with your self-signed SSL certificate:
That’s it! Close Keychain Access and restart Chrome, and your self-signed certificate should be recognized now by the browser. Warning: it will only work for certificates that have a correct hostname.