I have the a Looker instance (24.14.43) running on an ubuntu server, and it’s been running great for years, however we updated our SSL certs for looker and now the Chrome browser will not connect to Looker. It’s only a problem with Chrome (and Edge). Safari, Firefox, etc., all connect just fine and the SSL certificate/chain displays just fine with no issues (it’s an official Godaddy cert, not self-signed, etc.).
When attempting to access the Looker instance, we get a ‘connection closed’ error (ERR_CONNECTION_CLOSED), and even accessing looker by the native port directly results in the same error. We even tried changing the browser user agent, etc., but nothing works for Chrome. Is this a bug with the most recent Looker update? We’ve regenerated the SSL certs a few different ways to rule them out, but the connection closed error never goes away for Chrome. Anybody else experienced anything like this before?
If anybody comes across this issue in the future, I solved this problem (TLDR: use LibreSSL to generate your .key and .pem files
If you generate your looker.pem and looker.key using OpenSSL, you have to know which version of the openSSL tool you are using. Use this command to determine which fork of software your openssl command is using:
openssl version
It will either output LibreSSL x.y.z, or it will output OpenSSL x.y.z
That will tell you which fork of openssl is being used by the openssl command of your client (libressl is still using “openssl” as it’s command line tool name so as to maintain compatibility/familiarity I think). For whatever reason, the OpenSSL version of the openssl tool does not work, and will cause TLS handshake issues with Looker if you try to use those certs to generate your looker SSL certificate.
Instead, you must use the LibreSSL version of openssl to generate the looker.pem and looker.key files. You can install the LibreSSL version of openssl via homebrew, or your method of choice:
brew install libressl
Generate your .pem and .key files using LibreSSL and follow the rest of the Looker SSL deployment guide , and everything will work for all browsers. I really hope this helps somebody someday.
