pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account

Marcello Magaldi magowiz at
Thu Mar 21 10:00:47 EDT 2013

sorry I didn't understand, now using it seems to go on but
still fails to connect, maybe for another issue, now I get :

(14:40:01) Session Management: Received first save_yourself
(14:40:01) Session Management: Received save_complete
(14:40:05) account: Connecting to account magowiz at
(14:40:05) connection: Connecting. gc = 0x7fb140716080
(14:40:05) dnsquery: Performing DNS lookup for
(14:40:05) dnsquery: IP resolved for
(14:40:05) proxy: Attempting connection to
(14:40:05) proxy: Connecting to via using HTTP
(14:40:05) proxy: Connection in progress
(14:40:05) proxy: Connected to
(14:40:05) proxy: Using CONNECT tunneling for
(14:40:05) proxy: HTTP proxy connection established
(14:40:05) proxy: Connected to
(14:40:05) jabber: Sending (****** <?xml version='1.0' ?>
(14:40:05) jabber: Sending (****** <stream:stream to='' xmlns='jabber:client' xmlns:stream='' version='1.0'>
(14:40:05) jabber: Recv (380): <stream:stream from=""
id="C870A83C8927E757" version="1.0" xmlns:stream=""
(14:40:05) jabber: Sending (********* <starttls
(14:40:05) jabber: Recv (50): <proceed
(14:40:05) nss:,O=Google Inc,L=Mountain
View,ST=California,C=US issuer=CN=Google Internet Authority,O=Google
(14:40:05) nss: subject=CN=Google Internet Authority,O=Google Inc,C=US
issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(14:40:05) nss: subject=OU=Equifax Secure Certificate
Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate
(14:40:05) certificate/x509/tls_cached: Starting verify for
(14:40:05) certificate/x509/tls_cached: Checking for cached cert...
(14:40:05) certificate/x509/tls_cached: ...Found cached cert
(14:40:05) nss/x509: Loading certificate from
(14:40:05) certificate/x509/tls_cached: Peer cert matched cached
(14:40:05) nss/x509: Exporting certificate to
(14:40:05) util: Writing file
(14:40:05) certificate: Successfully verified certificate for
(14:40:05) jabber: Sending (ssl) (****** <stream:stream to='' xmlns='jabber:client' xmlns:stream='' version='1.0'>
(14:40:05) jabber: Recv (ssl)(139): <stream:stream from=""
id="09E07D9E99739260" version="1.0" xmlns:stream="" xmlns="jabber:client">
(14:40:05) jabber: Recv (ssl)(197): <stream:features><mechanisms
(14:40:05) sasl: Mechs found: X-OAUTH2 X-GOOGLE-TOKEN PLAIN
(14:40:05) jabber: Sending (ssl) (******* <auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga=''
ga:client-uses-full-bind-result='true'>password removed</auth>
(14:40:06) jabber: Recv (ssl)(77): <failure
(14:40:06) sasl: Mechs found: X-OAUTH2 X-GOOGLE-TOKEN
(14:40:06) sasl: No worthy mechs found
(14:40:06) connection: Connection error on 0x7fb140716080 (reason: 2
description: Not authorized)
(14:40:06) jabber: Recv (ssl)(16): </stream:stream>
(14:40:06) account: Disconnecting account *********
(14:40:06) connection: Disconnecting connection 0x7fb140716080
(14:40:06) jabber: Sending (ssl) (******** </stream:stream>
(14:40:06) connection: Destroying connection 0x7fb140716080
(14:40:06) util: Writing file prefs.xml to directory
(14:40:06) util: Writing file /home/*******/.purple/prefs.xml
(14:40:06) util: Writing file accounts.xml to directory
(14:40:06) util: Writing file /home/********/.purple/accounts.xml

I also used the workaround contained here
I didn't solve.

2013/3/21 Daniel Atallah <datallah at>

> On Thu, Mar 21, 2013 at 9:22 AM, Marcello Magaldi <magowiz at>
> wrote:
> > thanks Daniel, I read the answer you pointed me but the solution is not
> > doable in my case since I'm at work and I cannot configure network
> > infrastructure, I can only modify my machine configuration . Is there a
> way
> > I can fix this issue only modifying mine machine configuration ?
> The FAQ entry that I pointed at has a workaround listed (to set the
> Connect Server field in the Advanced account settings to
> "" ).
> -D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Support mailing list