Opened 5 years ago

Last modified 5 years ago

#16409 new defect

Can not enable account via Pidgin, but can use account via web.

Reported by: Dardwizzle Owned by: MarkDoliner
Milestone: Component: AIM
Version: 2.10.10 Keywords: account login enable
Cc: jarome

Description

I have not used mt AIM account in a long time, but tonight I needed to use it, so I updated Pidgin to the latest version "Pidgin 2.10.10 (libpurple 2.10.10)". For some reason is shows my account as "jdurchak disabled", yet, it shows me as "Available" with a green circle to the left of my user name, but just above that is says "Received unexpected response from https://api.oscar.aol.com/aim/startOSCARSession: useTLS=1 is not allowed for non secure requests.".

If I log in to AIM via the web, "AIM http://www.aim.com/#" I am able to see one of my buddies as online, however, the person that I am trying to message who is also on Pidgin, is not showing online for me, nor for them. I do not understand why I can login and use AIM online on the AOL website, but for Pidgin, I can not enable my account. I have even tried just changing my password and while that succeeded to work online, I still can not get my account to enable on Pidgin. I am hoping you can help as I have not found existing tickets on the site that were able to help me. This is a huge issue as this is the only AIM app that is allowed on our network. Please help.

Change History (16)

comment:1 Changed 5 years ago by QuLogic

  • Component changed from unclassified to AIM
  • Keywords AIM removed
  • Milestone Patches welcome deleted
  • Owner changed from EionRobb to MarkDoliner

comment:2 Changed 5 years ago by Dardwizzle

I am just curious if anyone happens to have any ideas for me? Possibly some things to try? Again, everything had been working just fine previous to this. Then, like some one flipped a switch, Pidgin just stopped working and I would really like to get it working again. Thanks.

comment:3 Changed 5 years ago by jarome

Also see https://trac.adium.im/ticket/16834

Adium worked a day ago and now just has stopped.

comment:4 Changed 5 years ago by MarkDoliner

My best guess is that this is a server configuration issue on AOL's side. As in maybe they deployed a new server or servers and they behave differently than some of their others.

I've also seen this error. It's happened with a few of my accounts. Usually I'm able to connect successfully after a few attempts.

It's also possible that Pidgin IS behaving mildly incorrectly and maybe AOL is rolling out more strict checks during the connection process, but this seems less likely to me.

I'm inclined to wait a few days or weeks and hope this problem goes away.

comment:5 Changed 5 years ago by jarome

But AIM and Trillian both connect all the time, so if cannot be a server issue, AOL must have changed something.

comment:6 Changed 5 years ago by Dardwizzle

Are any of these replies from the Pidgin developers or just from other users? It doesn't appear that there is anything being done by the developers at all, and all the updates appear to be coming from other affected users.

I want to know what is being done by the Pidgin developers in order to track down and isolate this issue. Should I stop using Pidgin and use a different application? I have stood behind Pidgin for years but I don't see Pidgin standing behind it's users which is very frustrating. If I am mistaken and the Pidgin Dev's have been working on this, I do not see it in my ticket.

Please update me as to what is being done by Pidgin to track down and resolve this or I will just move on to Trillian which doesn't seem to be affected by this issue.

Thanks.

comment:7 Changed 5 years ago by MarkDoliner

I'm a Pidgin developer. I'm not doing anything to track down this issue.

If you try reconnecting 10 or 20 times, does it eventually connect for you? Or are you completely unable to login?

comment:8 Changed 5 years ago by Dardwizzle

I am completely unable to login to AIM using Pidgin. I have tried over the last few days and I have yet to be able to login it fails every time with the same error. If you guys have no intention of doing anything to help us figure out what is going on let me know and I will stop using Pidgin, though it has been my favorite AIM app since pidgin was released for Windows. I first started using it on Linux and when I found it was released for Win32/64 I started using it and I have been using it ever since. It would be ashame to have to give up using it, but that is completely up to you guys. Please let me know.

comment:9 follow-up: Changed 5 years ago by MarkDoliner

I currently have no plans to try to fix this.

comment:10 in reply to: ↑ 9 Changed 5 years ago by Dardwizzle

Replying to MarkDoliner:

I currently have no plans to try to fix this.

Can I ask why you guys have no plans on fixing this when it is obviously not allowing some people to be able to use Pidgin? It would appear that this is a large enough issue that something is broken, perhaps it's something that AIM has changed but if it is negatively effecting the use of Pidgin either you guys could careless about your users, or you don't feel that AIM changes are important enough to keep Pidgin up to date, either way, I am baffled why you guys have no interest in the fact that we can't use Pidgin anymore while other programs such as Trillian don't seem to be affected? I'm rather bewildered. Can you please shed some light on this?

comment:11 follow-up: Changed 5 years ago by QuLogic

The AOL developer site appears to have been taken down, so there is no documentation about what should be done differently here. The only available code I can find does the same thing that libpurple does. The only way to determine any differences is to reverse engineer the protocol again, and this is difficult because the connection is encrypted. And to top it all off, I just created a throwaway account on AIM (I don't have one; Mark might), and Pidgin was able to login without issue, so I can't even reproduce the problem.

Last edited 5 years ago by QuLogic (previous) (diff)

comment:12 in reply to: ↑ 11 Changed 5 years ago by Dardwizzle

Replying to QuLogic:

The AOL developer site appears to have been taken down, so there is no documentation about what should be done differently here. The only available code I can find does the same thing that libpurple does. The only way to determine any differences is to reverse engineer the protocol again, and this is difficult because the connection is encrypted. And to top it all off, I just created a throwaway account on AIM (I don't have one; Mark might), and Pidgin was able to login without issue, so I can't even reproduce the problem.

Fair enough! Hopefully the developer site will come back online or AOL reverts what ever they did that has caused this problem. I do appreciate the explanation though, makes total sense. The amount of work needed to be done to understand and engineer any kind of a fix is just not worth the effort right now.

Thanks for updating us and supplying us with the information.

comment:13 Changed 5 years ago by MarkDoliner

I'm not motivated enough to make time to work on it.

Also I still suspect that it's a server misconfiguration that AOL will fix, probably in a few days, hopefully not more than a few weeks. I'm not sure why other clients aren't affected... maybe they use a different login method than us?

comment:14 Changed 5 years ago by Dardwizzle

Pidgin is not the only one affected. I was reading that the client that is used on MAC, Adium is also affected. The person who reported it was having the exact same problem with login and getting the same error.

With the amount of effort needed for you guys to even try and identify the problem and a possible fix, I can see why you wouldn't be motivated to fix this. I would feel the same way. After the explanation as to what would be needed to identify and fix, I am not longer bothered by you guys not fixed this so no worries there. No complaints from me :)

comment:15 Changed 5 years ago by Robby

Adium and Pidgin share the same network-level code, libpurple.

comment:16 Changed 5 years ago by jarome

A more general issue with the AIM support is that Pidgin (Adium) seems to behave very poorly with the new "group chats". It is impossible to get rid of them from your buddy list (permanently) unless you use the real AIM.

And of course, file transfer with Yahoo has been broken for many years now.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!