[Pidgin] #11142: AIM/ICQ not logging in as of 2010-01-12

Pidgin trac at pidgin.im
Wed Feb 17 10:58:19 EST 2010

#11142: AIM/ICQ not logging in as of 2010-01-12
 Reporter:  dburkard  |        Owner:  MarkDoliner
     Type:  defect    |       Status:  pending    
Milestone:            |    Component:  AIM        
  Version:  2.6.5     |   Resolution:             
 Keywords:            |  

Comment(by deesto):

 Starting to get a bit silly here ... I can counter-confirm that this is
 not working in a fresh  install (as in, just installed a few minutes ago)
 of Fedora 12 64-bit, which is on a proxied network connection but not
 going through the proxy for AIM as it's not necessary (as explained
 earlier).  When I leave the settings at default (which includes both SSL
 and clientLogin being turned on) for adding a new account to a fresh
 Pidgin install with a fresh OTR plugin install, I get this:
 "Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable
 to connect to api.screenname.aol.com: SSL Connection Failed"

 If I disable "Use SSL" and reconnect, I get the same error.  If I then
 enable SSL and disable clientLogin, and then reconnect, the connection is
 made.  Again: this is a brand-new install, with no other settings, and the
 machine is behind a proxy, but the proxy is disabled in the Pidgin

 As for SSL and Pidgin: the fact that SSL was not enabled by default in
 earlier versions does not mean that the SSL option was not available at
 all, does it?  I tend to use SSL whenever possible.  I'm not looking to
 cite a riot here; the two issues just seem orthogonal.

Ticket URL: <http://developer.pidgin.im/ticket/11142#comment:67>
Pidgin <http://pidgin.im>

More information about the Tracker mailing list