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

Pidgin trac at pidgin.im
Wed Feb 17 11:24:48 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 darkrain42):

 Replying to [comment:67 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

 The symptoms you describe are '''not''' the ones that this issue is
 tracking (the error message is different).  Please file a new ticket and
 attach the full Help->Debug Window output of failing to connect to your
 AIM account.

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

More information about the Tracker mailing list