Has anyone run into current Chrome refusing to connect to a server using a self-signed cert? Works in Edge and Firefox, not Chrome, annoying. Anyone know of a workaround? (This is a dev/test server, so I'm ok w the self-signed cert until go-live, when it'll get a real one.)

On Windows Chrome uses the system store. On Linux it has its own store and needs a separate process (I think under settings --> search for certificates)

Windows on client and server, not working. Are you suggesting something I should try?

If your custom cert is signed by your own self-signed trust store, you may need to • trust not just the cert but the CA • including the full chain (the CA) in the server cert

^^^ yeah, weird it works in Firefox and Edge though. on Windows I feel like it's usually the same

Doesn't Chrome have its own trust store? Perhaps that is making a difference 🤔

On Windows I thought it didn't, but obviously I could be wrong

What's the actual error message? Is Chrome rejecting because of the trust chain or something else like the expiration or common name?

Uh, weird. Today it works fine, in Chrome. Maybe I should just go play guitar. Pffft.

ERR_SSL_KEY_USAGE_INCOMPATIBLE ☝️ that's the real error.

Agree. Why does it happen, in Chrome only? How did it fix itself overnight?

Yeah, Chrome started pushing updates last week that changed a BUNCH of TLS requirements. Requires larger key sizes, more cryptos are disabled by default and the key usage thing.

What an excellent SO answer! I'll pass it along to our networking guy, he's also the certs guy, I'm guessing the reason it started working again was that the local state file got deleted, or expired, or something.