The certificate for could not be validated

Steve Golub smgolub at
Thu Aug 29 14:32:21 EDT 2013

Thanks very much for the quick reply.
I've installed 2.10.7 and it seems to have fixed the issue.
Please close the ticket as successful.


Steve Golub
(917) 579-0962


 From: Daniel Atallah <datallah at>
To: Steve Golub <smgolub at> 
Cc: "support at" <support at> 
Sent: Thursday, August 29, 2013 2:16 PM
Subject: Re: The certificate for could not be validated

On Thu, Aug 29, 2013 at 1:59 PM, Steve Golub <smgolub at> wrote:

>Today for the 1st time this message started popping up:
>SSL Certificate Validation
>Accept certificate for 
>The certificate for could not be validated.
>The certificate is not trusted because no certificate that can verify it is currently trusted. 
>When I click on View Certificate I see this:
>Common name:
>Fingerprint (SHA1): 28:dd:89:d3:0a:a6:f0:a2:b9:f8:77:fc:55:fc:ab:85:18:de:13:ff 
>Activation date: Tue Jul 23 09:37:27 2013
>Expiration date: Wed Jul 23 09:37:27 2014
>I'm running Pidgin 2.10.6 (libpurple 2.10.6) on Windows 7.

Upgrade to Pidgin 2.10.7.

>What changed?  How do I get past it?

Google updated the Certificates.  There's a bug in older Pidgin versions that prevents the new certificate from being validated successfully.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Support mailing list