Adium Problem – Error: Socket is not connected
I ran into an annoying little problem last week – Adium was no longer able to connect with my AIM account. The error it kept giving me was “Adium problem – Error: Socket is not connected.” Frustrating!
After hunting around the web a bit and finding several headache-inducing solutions (involving deleting, uninstalling, reinstalling, etc), I found a forum comment that I thought worth a try. The solution? Simply go into Adium’s preference panel, choose the offending account and hit edit.
And chang the port to 80 from whatever it currently is (mine was 5190).
Then, voila! Success!
June 16th, 2008 at 11:32 am
D’oh, that should have been obvious. Thanks for posting this, it was helpful!
July 15th, 2008 at 7:12 pm
This is just the advice I was looking for. Worked perfectly. Thanks a bunch!
July 18th, 2008 at 1:05 pm
for some reason that hasn’t worked for me, it just said “screen name sent 20%” and hasn’t moved from there…
July 25th, 2008 at 11:06 am
Perfect, I was trying to figure out why Adium no longer worked at work!
August 30th, 2008 at 7:57 am
Great Worked a treat for mobile me, did originally try port 443 as i had seen a similar trick on another website but that didn’t work.
September 6th, 2008 at 4:18 pm
THANK YYOU SO MUCH, this has been a problem with adium for a while, that drove me crazy
September 12th, 2008 at 11:30 am
That was awesome!
October 5th, 2008 at 6:32 pm
You fixed my headache tonight! I’m at a conference in D.C., on wireless in my hotel, and I couldn’t figure out why Adium couldn’t connect, even though my browser and e-mail client were working just fine.
Thanks for posting this!
November 25th, 2008 at 9:58 pm
Terrific! Now I can get back to writing my new novel about identity theft!
December 14th, 2008 at 9:22 pm
Ahhh… success! Thanks very much for the tip!
December 18th, 2008 at 10:15 pm
Port 80 did not work, nor did 443 or 5222.
January 13th, 2009 at 6:09 pm
wow that really helped! simple and easy! thanks!
January 14th, 2009 at 3:00 pm
Port 80 and 442 (and the original 5222) don’t work for me. I get to “Reading Data (50%)” then it stops.
February 21st, 2009 at 8:05 pm
thank you so much, this was driving me insane!
March 9th, 2009 at 7:47 pm
this was so helpful, thank yoU!
March 14th, 2009 at 5:33 am
I must say, I could not agree with you in 100%, but that’s just my opinion, which indeed could be very wrong.
p.s. You have an awesome template for your blog. Where have you got it from?
March 18th, 2009 at 12:40 pm
hey that worked … you’re amazing.
May 10th, 2009 at 10:15 am
Thank you so much seriously i was pissssed last night when i couldn’t figure it out
thanks :)
May 12th, 2009 at 4:40 am
Brilliant! Thank you – but why port 80?
June 20th, 2009 at 9:56 am
Thank you so much for this!!
I was about to give up on Adium for the night and just see if it sorts itself out, but then I decided to do a quick Google search. This post appear near the top, and now my Adium is working fine.
All my accounts (AIM, MSN, gTalk) weren’t working and changing them to Port 80 fixed them.
Thanks again! :)
June 25th, 2009 at 2:29 pm
Bless you! This just happened to me after I upgraded this morning and I freaked out. Thank you for posting this! All fixed! :)
June 29th, 2009 at 10:21 am
Thanks, worked great.
July 30th, 2009 at 7:42 am
Thank you so much! It worked perfectly!
September 7th, 2009 at 7:44 am
Life Freakin Saver Dude!! Thanks a lot!!
September 20th, 2009 at 9:12 am
awesome! thanks!!
September 22nd, 2009 at 11:56 am
I had this problem with my school’s wifi. They’ve obviously blocked the “traditional” IM ports; 80 is the port used for HTTP, though, so they can’t block that.
Thanks! It was bugging me that I couldn’t connect on my school’s network.
October 12th, 2009 at 1:54 pm
Frndz, i had the same problem and found the solution….
when i install it i had used ethernet cable so i could not use it when i use wireless connection which is using DHCP. hence i have changed it port 80 when i using the wireless it is working fine but i could use the old port when i connect it through ethernet cable/
October 16th, 2009 at 2:21 pm
It was not the answer for me either, but thanks for putting it up anyways, it worked for so many I had high hopes, but alas, I was shot down yet again. Thank god for google talk.
October 27th, 2009 at 10:26 am
You can also try port 8080 if you are behind a firewall that you have no control over (ie. work/school/hotel). It worked for me just fine when neither 80 or 442 worked.
November 18th, 2009 at 10:22 pm
Hey thanks a lot..that fixed my problem too…
:)
February 23rd, 2010 at 9:36 pm
that did it — thanks mani!
March 1st, 2010 at 12:08 pm
wow thx! I didnt know why adium wasn’t working and it was driving me crazy! thx a lot!
May 13th, 2010 at 12:08 pm
THANK YOU SO MUCH! i was going totally bonkers trying to figure out what was wrong. you are a lifesaver.