Archive for the ‘Pidgin’ Category

I can’t verify that this will work anywere else in the world. It works for me with Pidgin 2.6.6, with a machine sitting in Cape Town, South Africa connected via MWEB.

  1. Download & Install the latest version of Pidgin.
  2. Open Pidgin and go to Add / Edit Account window of Pidgin.
  3. From the drop-down box choose XMPP as the Protocol.
  4. For the Screen name enter your Google Id (Gmail Id). eg. ubuntupunk (without any @ symbol or domain).
  5. Server will automatically populate with gmail.
  6. Leave password blank and save password unchecked
  7. Under Advanced: Force old (port 5223) SSL: Checked
  8. Allow plaintext auth over unencrypted streams: Un-Checked
  9. Connect Port: 443
  10. Connect Server: talk.google.com
  11. Proxy type: Use Gnome Proxy Settings
  12. Start Pidgin. It should ask for password, enter and check save password


1. Under accounts. Scroll down to your account. Check to see if actions are available. If they are not then there is something wrong.

2. Go to this site

3. Invite yourself to Gtalk to VOIP.

4. Log into you Gmail Account.

5. Check to see if the invite has arrived.

6. Accept the invitation

Other guides




Read Full Post »

Skype plugin for Pidgin

Get your Skype contacts in Pidgin


Read Full Post »

And there I was thinking it was my proxy service on the blink since I haven’t paid my bill for months. Turns out the latest Pidgin update is decidedly proxy unfriendly:

Pidgin 2.6.4 Changes Proxy Behavior Filed under: Miscellaneous, Tools — Julian @ 10:11 pm I use Pidgin for all of my IM functions including Facebook and Skype and I love the application. I especially like the OTR plug-in that allows me to have “private” conversations with my buddies regardless of the underlying protocol being used. I also use the Portable Apps version so that I can “take” my contacts, history, and other settings with me. I recently updated to the 2.6.4 version and after the update completed and I started Pidgin, I was unable to connect to any of my accounts. I use a remote HTTP proxy server to relay my IM connection so that restrictive corporate firewalls don’t block my IM accounts. I opened the debug window and after seeing the “Access Denied” message, I thought that it might be the proxy server itself. After verifying that nothing in the server configuration has changed recently, I started to look at other possibilities. I was able to configure Firefox to use the proxy server successfully, so I started to look at the Pidgin client as the culprit… I did a quick Google search and I found the reason. In the change-log for version 2.6.4 is a line in the libpurple component:

* Don’t send Proxy-Authorization headers to HTTP proxy servers until we’ve received a “407 Proxy Authentication Required” response from the server. (thecrux)

For some reason, the Squid Proxy Server that I use does not send this 407 response back and Pidgin never sends the credentials. So of course the Proxy Server replies with Access Denied since it does not allow unauthenticated users to use it. I’m sure that the developers fix the problem for a good reason, but it is still frustrating that existing working behavior in one version stops working in the next version. Until I can upgrade the Squid server or figure out how to make it send the 407 response, I’ll stay at version 2.6.3…

Thank you Julian, I would never have figured this out if it were not for your enlightening posting on the problem


Read Full Post »

This is where I am putting configuration information for Pidgin

Configure for Google

Configure for Yahoo

Configure for Twitter

Read Full Post »