Jan
12
by Peter Ridge
Today, my Pidgin IM client started giving the error, “Received unexpected response from http://api.oscar.aol.com/aim/startOSCARSession”, when connecting to the AOL Instant Messenger (AIM) server. Apparently, it can also happen when connecting to ICQ. Fortuantely, the fix/workaround on Windows and Linux is really easy.
- Go to Accounts
- Modify the AIM or ICQ account
- On the Advanced tab, clear the checkbox labeled Use clientLogin
- Save
Are you using Adium? It may also have this issue on the Mac. If you’ve solved it, post the steps in a reply.
Update: Alternatively, in step 3, you can clear the checkbox labeled Use SSL
Thank you, it worked.
any idea what they changed?
Not sure what changed. It happened to me on 2.6.4 and I got notification that 2.6.5 was out. So, I updated, but it didn’t fix the problem. If you run into any more info, let me know.
The 4-step fix seems to work for me.
This error is weird. I only got it when I upgraded this morning to Pidgin 2.6.5. So I said “screw this” and reinstalled 2.6.4… but the error was still there!
unmark SSL in the connection settings of the pidgin and u’ll be able to connect
You are a godsend (if atheistic, um…you are a coincidence of genes that was really really useful to me); I had felt like an idiot for an hour trying to figure that one out.
@ Kelsey: “a coincidence of genes that was really really useful” LOL! That’s a new one. Glad it worked out.
That worked. I had the same symptoms as everyone else. Thanks for the tip!
Unmarking SSL did the trick for me. Never had this problem until 2.6.5. Thanks for posting the solution.
thanks so much for this fix!! worked like a charm. :)
Had the same problem in both 2.6.4 and 2.6.5 (Windows). Unchecking the clientLogin tickbox worked perfectly. Thank you so much!
Thanks for the quick fix. MUCH appreciated… worked great on 2.6.4 win7 x64!
I’m using Pidgin 2.6.5, and while disabling SSL worked, disabling ClientLogin definitely worked better. :)
Just had this problem happen literally >10 minutes ago.. Googled and voila, your post was made four hours ago. Life saver ;)
Oh christ, thank you. That was driving me nuts.
Thanks for this! I have been trying to log in all day, but failed. Thanks again!
Thanks.
It works fine.
Thank you so much! This was bugging me all morning!
Thanks, worked for me. I was about the post a solution as well to my blog, but found this, and it’s also noted on pidgin.im as well.
I had the same problem. Steps 1-4 worked fine for me. Thanks for posting the fix.
Thanks for posting the fix. I’m amazed how many people have had the same issue. Is there any idea on the root cause of this?
Those 4 steps worked for me. Thanks!
Thank you, that was it.
Same thing… your fix seemed to do the trick. But it was only on an install on a Vista system… my Win 7 was still working as of this morning.
I was using 2.6.4 just fine until Tuesday 1/11/10 when the error started happening. I upgraded to 2.6.5 but that didn’t help. I tried unchecking SSL and that worked so I tried re-checking it and unchecking Use ClientLogin and that worked too. So both options worked for me.
Thanks, that helped me fix my panic with Adium 1.5…
Thank you!!!
@Droas: Interesting that turning off clientLogin worked better than disabling SSL. Thanks for the info. In what way(s) did it work better?
@Jason Dowdell: I’m not sure what the root cause is. However, I just recalled that there was a Windows Update yesterday too. But, I don’t remember if I updated and rebooted Windows before or after my Pidgin stopped connecting.
Yet another one saved by this article. Also had trouble logging into 2 AIM accounts on 2.6.4 and 2.6.5.
It’s great that there are some smart people in this world
Many thanks
Perfect, thank you very much.
Thank you for posting this. It was getting frustrating to have to login to gmail to access my AIM accounts. I didn’t want to actually have to resort to downloading the official AIM app…
Here’s the pidgin.im Trac entry on the underlying cause: http://developer.pidgin.im/ticket/11142
Thank you! That’s been bugging me all night. Also, for reference, I definitely started getting the error _before_ installing the Windows Update.
Excuse my naivety, but what are the repercussions of unchecking clientLogin? I mean, I assume there was a reason that was checked by default.
@Dan: Thanks for the Trac link!
@Kevin: I believe unchecking the clientLogin tells Pidgin to use a different interface to communicate with AIM servers. From the Trac link that Dan posted, the trouble ticket indicates that Pidgin is requesting a secure connection from a non-secure service URL. It used to work but doesn’t anymore. Sounds like the old server behavior wasn’t quite right (even though the interface docs said it was OK) and AOL fixed it.
This worked really well for me under Ubuntu linux.
Thanks! This worked wonders for me on Arch Linux using Pidgin 2.6.5.
thank you!!!! i was starting to go crazy
Thanks, clearing the clientLogin box fixed the problem.
Ohhhh, THANK you! This error was driving me crazy for the last week or two, and today I just couldn’t get things to load at ALL… but this has solved everything.
I give this tip five stars.
Thanks
Thanks!! Probably the easiest workaround I’ve seen in quite some time!
Thanks! That worked like a charm!
Thanks! Worked for me as well. (running 2.6.5)
Thank you it worked on Windows Vista Pidgin 2.6.6
thanks :)
Thanks
Thank you for the help… Saved me a day of headache!
Thank so much. :)
Thanks!
Thanks for the tip. I updated just couple days ago, and did not have to research the issue. My first google search led to your tip and it solved it in a couple seconds! Good coincidence of genes indeed! :)
Thank you so much!
Mine was already unchecked when I got to it. It still won’t work. What should I do?
Never mind. I was looking in the wrong spot. Works now.
Much thanks.
Your fix work for me
Thank you
Got it going again…thanks, buddy!
Why the * are u all so happy with disabling secure message transfer???
Disabling SSL will send all messages and the login sequence in plain text ready to view and intercept by anyone on the net.
Disabling SSL is not an option, so what else can be done?
@Martin. Pidgin does not send your password in the clear, even when using an unencrypted connection. Your password is hashed with a token from AOL’s server before it’s sent. Nevertheless, this problem was a bug with AOL’s servers and has since been rectified. So, there is no longer any need to turn off clientLogin or SSL. See http://developer.pidgin.im/ticket/11142
@Peter Ridge. The link you provided was last updated 8 months ago and the problem was resolved 10 months ago. Do you have a more recent link that states the problem from this occurance?
@Brian. Sorry, I’m not following. This problem has already been resolved. Martin was questioning the workaround, so I replied to that. There isn’t any new occurrence regarding the original problem. Are you still having the problem with the latest version?
I am still having the problem with Pidgin 2.6.6 and I just updated and am still having the same problem. i have unticked both the SSL and Client Login. I have set my proxy to No Proxy with no luck. Getting a little frustrated with this since I use ICQ for work and I can’t get logged in from home.
After further searching I found this and thought I would share.
Change server to login.icq.com
(ssl – off, client login – off)
Thanks, Rob.
These are my results, on pidgin 2.6.6, linux
SSL/ClientLogin
on /on : error: unexpected response etc…
on /off: error: unknown reason
off/on : OK!
off/off: error: unknown reason