RE: "Unable to validate certificate"

Saw that, but it *seems* slightly different. Weirdly, after getting them all evening and night (based on the number of popups I had to close!), I got a few throughout the morning and then they stopped. So maybe it really was a Google problem--maybe one server behind a LB with a bad cert?

Re: "Unable to validate certificate"

Similar issue here: The certificate for 0.client-channel.google.com could not be validated. The certificate is not trusted because no certificate that can verify it is currently trusted. There's an issue on Bitbucket:

Re: "Unable to validate certificate"

It didnt say it could not remember. It said it cant validate. Very different. -- Registered Linux User: #480675 Registered Linux Machine: #408606 Linux since June 2005 On Fri, Jan 5, 2018 at 4:27 PM, wrote: > I am still getting those popups. > > Why wouldn't Pidgin

"Unable to validate certificate"

After running flawlessly for a while, I'm suddenly getting: Unable to validate certificate The certificate for clients6.google.com could not be validated. The certificate chain presented is invalid. This happens repeatedly at random intervals. Sometimes I get several of these dialogs at once,

Re: "Unable to validate certificate"

I am still getting those popups. Why wouldn't Pidgin remember the accepted certificate? On 05/01/2018 10:04 PM, Phil Smith III wrote: Saw that, but it *seems* slightly different. Weirdly, after getting them all evening and night (based on the number of popups I had to close!), I got a few