Rebuild with Newer Root Certificates - Unable to Connect to All Addresses Error

[steve-gray]

Hey folks,

There's another issue related to this the reporter has closed, but #402 is becoming increasingly a problem now. In the nearly 7 months since the last build, many root CA's have updated their certificate chain. Would it be possible to get a rebuild/updated version pushed and updated on Brew please? No code changes in principal, just an updated electron bundle/certificates.

The specific problem is that the bundle that shipped with the last build doesn't have trust for ISRG Root X1 from LetsEncrypt, which most recently issued certificates are backed by. I spent the best part of a few days debugging random ingress issues and firewall stuff, I stumbled onto the issue.

[Metalscreame]

+1, due to this it's impossible for me to use right now

[nlflint]

I had the same issue, can't use this tool with our GRPC services on a k8s cluster with LetsEncrypt signed ingresses. There is a workaround: import the Let's Encrypt CA into BloomRPC yourself.

1. Open a Let's Encrypted secured website in your browser, click the padlock, and go thru the UI to export a Let's Encrypt CA pem file.
2. Or find another way to get Let's Encrypt's CA into a PEM file format on your workstation.
3. In BloomRPC, click the TLS control and add the root cert
4. Select your new cert via the radio button and click Done
5. Should work now.

Also, I recommend saving your Environment after importing the CA. Then you can recall it easily on new bloomRPC tabs via the ENV dropdown, and you dont have to import the CA over and over again on every new tab.

[Metalscreame]

Thanks. This solution worked for me. Sadly is a temporal due to cert will expire:(