4 ms·
Very odd, I'm on the same release (Catalina) and no difficulties. The certificate is from Google Trust Services, which presumably Chrome should honor. Perhaps
by macintux 5y ago
Very odd, I'm on the same release (Catalina) and no difficulties. The certificate is from Google Trust Services, which presumably Chrome should honor.
Perhaps you have a proxy causing interference?
As the sibling comment notes, looking at the certificate using Advanced may help clarify things.
Update: here's the full chain that I see:
web.dev, signed by GTS CA 1D2, with a root certificate of GlobalSign Root CA - R2.
- Jemaclus 5y agoThis is what I see: https://d.pr/i/8VY9As https://d.pr/i/8VY9As As far as I know, I have no proxies to interfere...
- macintux 5y agoApparently there's still more to see if you dig deeper, but I'm unfamiliar with Chrome's UI for invalid certificates. If you can open your terminal, this may be easier: % openssl s_client -connect web.dev:443 It will hang (I guess awaiting more commands) but you can use Control-C to kill the connection. The gist below has the first several lines showing what you should see. https://gist.github.com/macintux/68ab1317d4b7677951069baf95cdee4c https://gist.github.com/macintux/68ab1317d4b7677951069baf95c...
- Jemaclus 5y agoOK, I think I see what's happening. There's some other software that overrode the *.dev cert. I'll remove that and see if it works. Thanks for your help!
- macintux 5y agoHuh, that's...unexpected. My best guess was that somehow the root certificate was missing from your computer's trusted certificate store. Glad you got it sorted, happy to help.
- abraham 5y agoIt was a fairly common issue when .dev first launched. https://andycroll.com/ruby/clean-up-broken-dev-domains-after-puma-dns_probe_finished_nxdomain/ https://andycroll.com/ruby/clean-up-broken-dev-domains-after...