4 ms·
I got a bunch of those errors in chrome a year or so ago - turned out I was on a really old version of Chrome (I didn't realise auto-update wasn't working on th
by allannienhuis 8y ago
I got a bunch of those errors in chrome a year or so ago - turned out I was on a really old version of Chrome (I didn't realise auto-update wasn't working on their Beta stream at the time), and some ssl cert chain configs became stale (or something like that). Updating my browser fixed it.
- tchaffee 8y agoI'll check it out, but I get frequent updates for Chromium and Chrome. I'm usually on the latest stable release. Thanks for the suggestion.