My primary employer uses Pidgin server. Starting off they required the Pidgin client. I had so much trouble keeping it working on Win7 I ave up and installed SWIFT. I have had one resinstall (after forced downgrade to Win10) since, and no problems on my Linux desktops.
I do not run Ubuntu now, so I cannot claim this will work for you, just that it might be soemthing to try.

A while back I had to stop using Pidgin because Google was blocking any "non official" client. Maybe they're at it again? Are there any error messages?

Thank you for your response, Mr. or MS. wpeckham!

I twice was asked for my password. Which I supplied. The way I know it's the right password is a)I get logged on to my gmail account and Chrome with that password; and b)I use KeePass2 for my password manager and that has the same password in it. After those two requests for my password, the only message I ever go was "<MyUser Name> not authorized". And I couldn't connect.

I tried using jabber.org servers and that didn't help. Tried changing the authorization method to good old SSL. Made sure I had my password right (rinsed and repeated several times.) Used Synaptic to remove Pidgin and then reinstalled.

So, while you could be right, it would have to be in the authorization from Google, because when not using Google servers, I am still "Not Authorized".

Had a "wake you up at 3:00 AM thought" that I should remove Pidgin again and grep for all files that might be left over. Even with using Complete Removal, I know that user data files are left behind. (Sorry, shiver down my spine -- reminds me of Windows. But Windows leaves all kinds of shit behind.)

Are we allowed to say "shit" on this board? Or am I supposed to type sh*t?

Solved it myself by switching to Port 80. Found it in a link hidden deep within the Official Pidgin Manual (https://support.google.com/a/answer/1279090?hl=en.) I REALLY don't like using port 80. Yes, I'm behind a NAT and have a firewall, but thinking of setting up a proxy since I have an older extra computer that ought to be able to handle proxy and nothing else.

GoogleTALK, then called CHAT, then HANGOUTS, then back to CHAT, is still GoogleTALK, or in its native service, "jabber". The server's name is still: TALK.GOOGLE.COM

Go to your domain management, login, and then click on the link below. It will take you where you can "allow less secure apps" (aka Pidgin) to login to GoogleTALK.

TURN "ON" LESS SECURE APPS ACCESS (for Pidgin to work)
https://myaccount.google.com/lesssec...ZNvNP3aG1OSifg


This should fix your issue, but sometimes takes a few hours to become "active".
I really cannot figure out why Google has it in for Pidgin, probably the VERY BEST chat utility that was ever conceived.

-rAllcorn-
Richard A. Allcorn (aka "Rich Allcorn")
eMail: rich@allcorn.us
personal website: http://rich.allcorn.us


P.S. No, uteck, Google whipped it up for me when my connectivity went down again for Pidgin and GoogleTALK.
... but thanks for the laugh!

Dude, did you really dig up a thread that was 5 years old to reply to it?
Granted the OP should have marked it solve back in 2016, but there is far newer post asking this same question by someone else you should have answered.

1 members found this post helpful.