Changed 5 years ago by Korich Attachment log.rtf added comment:28 Changed 5 years ago by Korich I use login/pass please, look this log comment:29 Changed 5 years ago by evands The comment:24 Changed 5 years ago by Robby Oh, right, it has been. :) Changed 5 years ago by Korich Attachment adium143_debug_proxy.txt added proxy debug comment:25 Changed 5 years ago by Korich proxy debug log.rtf (26.0 KB) - added by Korich 5 years ago. So, from here I saw that it was some kind of option in the client to "useTLS=1" for the entire scope of logging into AIM. http://amigasuperbit.com/connect-to/php-cannot-connect.html
Is it a bug? Does it work if you set encryption to disabled? I don't know why that would happen and I don't know how to debug it. Here's the debug from the latest fail: ...copying/pasting the text didnt work so well, so im attaching it in file form. https://www.pidgin.im/support/
Steps to reproduce Detail the exact steps taken to produce the bug. Where? Download Plugins Help About News Development Search: LoginHelp/GuideAbout TracMy NotificationsRegisterPreferences WikiTimelineRoadmapView TicketsView ReportsSearchAPI Context Navigation +0← Previous TicketNext Ticket → Opened 4 years ago Closed 4 years ago #15177 closed defect Your posting implied to me that this attempt had your proxy set, which I did not believe.
and the same for 1.5b3. more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed comment:46 in reply to: ↑ 45 Changed 5 years ago by deesto I'm glad to blame the proxy server if that turns out to be the culprit, but I would need a What Is Pidgin But should that matter, if the same error occurs when the proxy is bypassed?
comment:43 follow-up: ↓ 44 Changed 5 years ago by MarkDoliner There are a lot of comments on this ticket, can we summarize it? I have followed the "uncheck Use ClientLogin?" workaround and checked "CC me this Ticket" on #11142 to await a definitive solution. When it reconnected after the internet came back up, I guess the client and/or the AIM server (probably the latter as IRC had no problem with it) didn't like such a navigate to these guys I had set a stupidly-long away status (basically a text version of this), which was fine as long as I was connected, but while I was at work my internet briefly
comment:18 Changed 5 years ago by Korich ICQ not work via proxy too Error: Error requesting https://api.login.icq.net/auth/clientLogin: Unable to connect to api.login.icq.net: SSL Connection Failed comment:19 Changed 5 years ago by Pidgin Download I haven't tried to narrow it down past that (although a Google search seems to suggest that the bug may actually be in libpurple and was introduced with the libpurple revision Thanks. Download in other formats: Comma-delimited Text Tab-delimited Text RSS Feed Powered by Trac 1.0.2 By Edgewall Software.
comment:6 in reply to: ↑ 5 Changed 6 years ago by deesto Replying to sphynx: Okay, but what type? However, attempting https://api.oscar.aol.com/aim/startOSCARSession does not redirect nor deny (just won't do anything because it's not used for this direct purpose) and sets up a valid tls session. Unable To Connect To Authentication Server: Ssl Connection Failed comment:61 Changed 4 years ago by Robby Milestone changed from Adium 1.5.1 to Adium bugs comment:62 Changed 3 years ago by clawson I'm *not* using a proxy, but I'm having this Pidgin Portable Maybe they changed the API.
comment:15 Changed 5 years ago by evands Please post the debug log of your proxy failing to allow connection (that is, 'Systemwide HTTP settings' in 1.4.2b2). http://amigasuperbit.com/connect-to/pc-cannot-connect-to-network.html This is called a regression and should be reported as a bug. Yes I did, 3 weeks ago, via private message, as per request. Is this being looked at for 1.5? Pidgin Skype
This results in debug output: 13:31:57: (Libpurple: proxy) Connecting to api.screenname.aol.com:443 via localhost:8181 using HTTP Versus your log which shows 10:52:08: (Libpurple: proxy) Connecting to api.screenname.aol.com:443 with no proxy Please show I can, however, telnet to telnet 188.8.131.52 5190; if you can't do that, fixing that should fix your connection problem. comment:13 follow-up: ↓ 14 Changed 7 years ago by paulb104 I have been using Pidgin since December 1, 2009. navigate here And this is with "no encryption" set in Options (which I would prefer to set to "require").
I received an error when attempting to login into my Aim account "You have been connecting and disconnecting too frequently. Pidgin Messenger Note: See TracTickets for help on using tickets. However only the Pidgin client was affected, I was able to login via regular AIM.
This ticket was about a related, but likely different issue. My computer died (battery) and when I restarted and started Pidgin, everything worked great except for AIM. cl comment:63 Changed 3 years ago by sphynx clawson: There's a number of different issues reported here, some of which were solved and that makes it very confusing. Aol Instant Messenger comment:7 Changed 6 years ago by deesto Just downloaded and re-installed Adium v1.4.1 over existing version, and it works again, without changing any settings.
I usually assume user error when I have a problem ;) Guess I'll be submitting my first Ubuntu bug today. –David Apr 12 '12 at 15:34 add a comment| Your Answer Note: See TracTickets for help on using tickets. And as mentioned, the proxy setting "Systemwide HTTP settings" still works without a hitch in v1.4.1 (just tried it again now). http://amigasuperbit.com/connect-to/pc-cannot-connect-to-internet.html Download all attachments as: .zip Oldest first Newest first Threaded Comments only Change History (69) comment:1 Changed 6 years ago by sphynx Component changed from Adium Core to Service/AIM comment:2 follow-up:
At the moment I use a web based client at school to get around this problem now. comment:47 follow-up: ↓ 48 Changed 5 years ago by Robby deesto, have you contacted evands yet? However, to this point, I've found that for whatever reason, IM clients did _not_ need to have the proxy set, either explicitly or via system settings, in order to connect to Connection timed out". 2.5.5 runs fine, however.
Are these statements all accurate: Adium can't connect to https://api.screenname.aol.com:443 It fails both with and without an HTTP proxy It fails regardless of the Encryption setting (none/when available/always) You believe HTTP comment:39 in reply to: ↑ 38 Changed 5 years ago by deesto Replying to evands: deesto, you said that you use no proxy server at all in other clients. But as of right now, this is one of 2 issues we have left before we can release 1.4.3. comment:12 Changed 5 years ago by evands Milestone set to Adium 1.4.2 Severity changed from normal to regression comment:13 in reply to: ↑ 11 Changed 5 years ago by deesto Replying to
My gut feeling is the blame the proxy server. comment:8 Changed 8 years ago by datallah Resolution set to worksforme Status changed from new to closed Note: See TracTickets for help on using tickets. So the section for setting of ICQ in "accounts.xml" must looks like the second file and I was able to connect to my ICQ accoun using the last Pidgin version (V2.6.4) Do not post confidential information, especially passwords!
Adium 1.4.2 enables clientLogin, 1.4.3 disables it whet using proxy, and the result is that I can use the AIM account with 1.4.2 but not with 1.4.3 (SSL connection fails). Browse other questions tagged 11.10 empathy pidgin or ask your own question. comment:6 Changed 8 years ago by bernmeister Is this still an issue? I've confirmed that another client (iChat) can connect my AIM account without issue when no proxy is set in the client.
Download Plugins Help About News Development Search: LoginHelp/GuideAbout TracMy NotificationsRegisterPreferences WikiTimelineRoadmapView TicketsView ReportsSearchAPI Context Navigation +1← Previous TicketNext Ticket → Opened 7 years ago Closed 7 years ago #9680 closed defect Is that web browser configured to use the proxy for HTTPS traffic? comment:6 Changed 6 years ago by clacke Suddenly had this problem today. Long story short -- my fault.