[WPPA+ dbg msg: Photo 0 does not exist in call to wppa_get_picture_html(). Type = From : wppa-picture.php line: 44 in function wppa_get_picture_html - wppa_initialize_javascript - apply_filters - do_action]

Poojan (Wagh) Blog

Requests for comment

Setting up Pidgin for Google Talk behind an http proxy (web proxy / corporate firewall)

with 3 comments

I use Google Talk at work mainly to post to social networks (army.twit.tv, identi.ca, twitter.com, yammer.com). It is possible to receive notification using Google Talk (which is just a Jabber/XMPP instance), but I find that too intrusive to what little work I get done.

  1. Run pidgin (if not already) and select Accounts->Manage

  2. Select Add to add another account:

  3. Select XMPP for the protocol type:

  4. Fill out the form as follows with gmail/gtalk username & password; domain is gmail.com; Resource is (optionally) Work:

  5. Click advanced button. Select old (port 5223) SSL. Select 443 for port number. Server is talk.google.com. Fill out http proxy (for example, wwwgate0.example.com, port 1080) & http-proxy username & password (not likely the same as your gmail username/password):

This works because http proxies generally allow ports 80 (http) and port 443 (SSL/https) through. They generally disallow other ports. Luckily, google’s jabber server (talk.google.com) accepts connections on port 443–and they are SSL (encrypted) connections, so that’s good, too.

Written by PoojanWagh

October 13th, 2008 at 3:11 pm

3 Responses to 'Setting up Pidgin for Google Talk behind an http proxy (web proxy / corporate firewall)'

Subscribe to comments with RSS or TrackBack to 'Setting up Pidgin for Google Talk behind an http proxy (web proxy / corporate firewall)'.

  1. Have you thought about using the ‘Require SSL/TLS’ option while connecting via proxy? Because it is not checked in the last screenshot.

    Dominik

    30 May 13 at 1:12 pm

  2. @Dominik: When I wrote this, the right thing to do at the time was to use “Old SSL” (port 5223). I no longer have his setup, but I imagine that regular TLS/SSL probably works now with Google’s servers (and maybe it always did–it might have been my proxy that didn’t like it).

    PoojanWagh

    9 Aug 13 at 9:02 am

  3. Awesome! Thanks in advance!

    Minari

    3 Feb 14 at 5:32 pm

Leave a Reply