Allego una versione italiana di questo post al fondo.

I’m using right now Adium X 1.0.1 with three IM accounts (ICQ, MSN and Google Talk). This great software uses the same GAIM libraries for managing the IM connections.
Adium works nice for me, but not with all the internet connections. With some providers I can’t connect with Gtalk. The problem is very strange and annoying: the message is “SSL Handshake Failed“. I cannot debug it, because this problem will not occur always, even with the same conditions (connection type, latency, IP address, etc…).

Today, I have found a solution…

Google Talk is a network compatible with the Jabber standard. Into the Google Talk Help, GAIM section, the how-to says to use the 5222 port when adding the Jabber/GTalk account. My fix is to replace the port 5222 simply with the port 80. I have got this idea reading some posts about the ability of Jabber/Gtalk to bypass some firewalls.

Adium Google Talk config detail
This is a screen shot of my config panel

Breve riassunto in italiano: modificate la porta da 5222 a 80 nella configurazione di connessiona GTalk e l’errore “SSL Handshake Failed” dovrebbe sparire. 🙂


P.M.S.Prakash · April 12, 2007 at 20:06

Actually this changing the port number may not be required. The server name should be changed to “” instead of and it worked with the original settings itself.

I found this updated instructions in google site.

Graham C · July 23, 2007 at 14:45

This ‘fix’ was concerning the problems with connecting behind a proxy server. And I have not had any success with it when trying to connect behind my HTTP proxy on port 8080.. maybe if it was a SOCKS proxy this would work..

Shaun · October 25, 2007 at 14:27

Thanks for this, I’d been have trouble with this since I changed web providers. It is nice to have found a solution.

Dan · December 9, 2009 at 18:25

THANKS!! Nice and easy, a perfect solution!

melanie · March 10, 2010 at 16:18

THANK YOU!!! Worked for me – my problem with connecting is limited to certain wireless connections and this solved it. 🙂

tomer · June 30, 2010 at 00:05


popen2 · July 9, 2010 at 13:11

Thanks!! Works perfectly 🙂

Barbarag · July 12, 2010 at 17:28

Changing to port 80 worked for me. Thanks.

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *