Re: pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account
On Thu, 21 Mar 2013 10:28:49 +0100 Marcello Magaldi wrote: Is there any possibility I can connect in this situation ? I also tried to change proxy type but I didn't get connected. Latest Pidgin version is 2.10.7, it might help. -- Brian Morrison ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
Re: pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account
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 ? 2013/3/21 Daniel Atallah datal...@pidgin.im On Thu, Mar 21, 2013 at 5:28 AM, Marcello Magaldi mago...@gmail.com wrote: Hi all, I'm trying to configure my gmail account to make it work behind an HTTP proxy, I set IP, port, proxy username and proxy password correctly into proxy tab of mine account, pidgin tries to connect, and after a while (after line that contains xmlns:stream='http://etherx.jabber.org/streams into log) I got a disconnection. The log follows , obviously I replaced my usernames with (*) and proxy IP with (xxx) : (10:14:42) account: Connecting to account **@gmail.com/. (10:14:42) connection: Connecting. gc = 0x7f2476513230 (10:14:42) dnssrv: querying SRV record for gmail.com: _xmpp-client._tcp.gmail.com (10:14:47) util: Writing file accounts.xml to directory /home/***/.purple (10:14:47) util: Writing file /home/*/.purple/accounts.xml (10:15:02) dnssrv: res_query returned an error (10:15:02) dnsquery: Performing DNS lookup for xx.xxx.x.xxx (10:15:02) dnsquery: IP resolved for xx.xxx.x.xxx (10:15:02) proxy: Attempting connection to xx.xxx.x.xxx (10:15:02) proxy: Connecting to gmail.com:5222 via xx.xxx.x.xxx:8080 using HTTP (10:15:02) proxy: Connection in progress (10:15:02) proxy: Connected to gmail.com:5222. (10:15:02) proxy: Using CONNECT tunneling for gmail.com:5222 (10:15:02) proxy: HTTP proxy connection established (10:15:02) proxy: Connected to gmail.com:5222. (10:15:02) jabber: Sending (**@gmail.com): ?xml version='1.0' ? (10:15:02) jabber: Sending (**@gmail.com): stream:stream to=' gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' (10:15:21) autorecon: do_signon called (10:15:21) autorecon: calling purple_account_connect (10:15:21) account: Connecting to account @gmail.com/. (10:15:21) autorecon: done calling purple_account_connect (10:18:11) connection: Connection error on 0x7f2476513230 (reason: 0 description: the server closed connection) Is there any possibility I can connect in this situation ? I also tried to change proxy type but I didn't get connected. The problem you're running into isn't really related to the proxy - see this FAQ entry: https://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#gtalk_srv -D ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
Re: pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account
On Thu, Mar 21, 2013 at 9:22 AM, Marcello Magaldi mago...@gmail.com 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 talk.google.com ). -D ___ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
Re: pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account
sorry I didn't understand, now using talk.google.com 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 mago...@google.com/. (14:40:05) connection: Connecting. gc = 0x7fb140716080 (14:40:05) dnsquery: Performing DNS lookup for xxx.xxx.xxx.xxx (14:40:05) dnsquery: IP resolved for xxx.xxx.xxx.xxx (14:40:05) proxy: Attempting connection to xxx.xxx.xxx (14:40:05) proxy: Connecting to talk.google.com:5222 via xxx.xxx.xxx.xxx:8080 using HTTP (14:40:05) proxy: Connection in progress (14:40:05) proxy: Connected to talk.google.com:5222. (14:40:05) proxy: Using CONNECT tunneling for talk.google.com:5222 (14:40:05) proxy: HTTP proxy connection established (14:40:05) proxy: Connected to talk.google.com:5222. (14:40:05) jabber: Sending (**@google.com): ?xml version='1.0' ? (14:40:05) jabber: Sending (**@google.com): stream:stream to=' google.com' xmlns='jabber:client' xmlns:stream=' http://etherx.jabber.org/streams' version='1.0' (14:40:05) jabber: Recv (380): stream:stream from=google.com id=C870A83C8927E757 version=1.0 xmlns:stream= http://etherx.jabber.org/streams; xmlns=jabber:clientstream:featuresstarttls xmlns=urn:ietf:params:xml:ns:xmpp-tlsrequired//starttlsmechanisms xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismX-OAUTH2/mechanismmechanismX-GOOGLE-TOKEN/mechanism/mechanisms/stream:features (14:40:05) jabber: Sending (*@google.com): starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/ (14:40:05) jabber: Recv (50): proceed xmlns=urn:ietf:params:xml:ns:xmpp-tls/ (14:40:05) nss: subject=CN=talk.google.com,O=Google Inc,L=Mountain View,ST=California,C=US issuer=CN=Google Internet Authority,O=Google Inc,C=US (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 Authority,O=Equifax,C=US (14:40:05) certificate/x509/tls_cached: Starting verify for talk.google.com (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 /home//.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) certificate/x509/tls_cached: Peer cert matched cached (14:40:05) nss/x509: Exporting certificate to /home/***/.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) util: Writing file /home/***/.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) certificate: Successfully verified certificate for talk.google.com (14:40:05) jabber: Sending (ssl) (**@google.com): stream:stream to=' google.com' xmlns='jabber:client' xmlns:stream=' http://etherx.jabber.org/streams' version='1.0' (14:40:05) jabber: Recv (ssl)(139): stream:stream from=google.com id=09E07D9E99739260 version=1.0 xmlns:stream= http://etherx.jabber.org/streams; xmlns=jabber:client (14:40:05) jabber: Recv (ssl)(197): stream:featuresmechanisms xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismX-OAUTH2/mechanismmechanismX-GOOGLE-TOKEN/mechanismmechanismPLAIN/mechanism/mechanisms/stream:features (14:40:05) sasl: Mechs found: X-OAUTH2 X-GOOGLE-TOKEN PLAIN (14:40:05) jabber: Sending (ssl) (***@google.com): auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga=' http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'password removed/auth (14:40:06) jabber: Recv (ssl)(77): failure xmlns=urn:ietf:params:xml:ns:xmpp-saslnot-authorized//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 *@google.com/(0x7fb13f83e180) (14:40:06) connection: Disconnecting connection 0x7fb140716080 (14:40:06) jabber: Sending (ssl) (@google.com): /stream:stream (14:40:06) connection: Destroying connection 0x7fb140716080 (14:40:06) util: Writing file prefs.xml to directory /home/***/.purple (14:40:06) util: Writing file /home/***/.purple/prefs.xml (14:40:06) util: Writing file accounts.xml to directory /home//.purple (14:40:06) util: Writing file /home//.purple/accounts.xml I also used the workaround contained here https://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#WhydoIgetaServerdoesnotuseanysupportedauthenticationmethoderrorbut I didn't solve. 2013/3/21 Daniel Atallah datal...@pidgin.im On Thu, Mar 21, 2013 at 9:22 AM, Marcello Magaldi mago...@gmail.com 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
Re: pidgin 2.10.6 on Ubuntu 12.10: cannot connect behind a HTTP Proxy to gmail account
nevermind I replaced in Domain google.com to gmail.com and it worked . 2013/3/21 Marcello Magaldi mago...@gmail.com sorry I didn't understand, now using talk.google.com 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 mago...@google.com/. (14:40:05) connection: Connecting. gc = 0x7fb140716080 (14:40:05) dnsquery: Performing DNS lookup for xxx.xxx.xxx.xxx (14:40:05) dnsquery: IP resolved for xxx.xxx.xxx.xxx (14:40:05) proxy: Attempting connection to xxx.xxx.xxx (14:40:05) proxy: Connecting to talk.google.com:5222 via xxx.xxx.xxx.xxx:8080 using HTTP (14:40:05) proxy: Connection in progress (14:40:05) proxy: Connected to talk.google.com:5222. (14:40:05) proxy: Using CONNECT tunneling for talk.google.com:5222 (14:40:05) proxy: HTTP proxy connection established (14:40:05) proxy: Connected to talk.google.com:5222. (14:40:05) jabber: Sending (**@google.com): ?xml version='1.0' ? (14:40:05) jabber: Sending (**@google.com): stream:stream to=' google.com' xmlns='jabber:client' xmlns:stream=' http://etherx.jabber.org/streams' version='1.0' (14:40:05) jabber: Recv (380): stream:stream from=google.com id=C870A83C8927E757 version=1.0 xmlns:stream= http://etherx.jabber.org/streams; xmlns=jabber:clientstream:featuresstarttls xmlns=urn:ietf:params:xml:ns:xmpp-tlsrequired//starttlsmechanisms xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismX-OAUTH2/mechanismmechanismX-GOOGLE-TOKEN/mechanism/mechanisms/stream:features (14:40:05) jabber: Sending (*@google.com): starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/ (14:40:05) jabber: Recv (50): proceed xmlns=urn:ietf:params:xml:ns:xmpp-tls/ (14:40:05) nss: subject=CN=talk.google.com,O=Google Inc,L=Mountain View,ST=California,C=US issuer=CN=Google Internet Authority,O=Google Inc,C=US (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 Authority,O=Equifax,C=US (14:40:05) certificate/x509/tls_cached: Starting verify for talk.google.com (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 /home//.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) certificate/x509/tls_cached: Peer cert matched cached (14:40:05) nss/x509: Exporting certificate to /home/***/.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) util: Writing file /home/***/.purple/certificates/x509/tls_peers/talk.google.com (14:40:05) certificate: Successfully verified certificate for talk.google.com (14:40:05) jabber: Sending (ssl) (**@google.com): stream:stream to=' google.com' xmlns='jabber:client' xmlns:stream=' http://etherx.jabber.org/streams' version='1.0' (14:40:05) jabber: Recv (ssl)(139): stream:stream from=google.com id=09E07D9E99739260 version=1.0 xmlns:stream= http://etherx.jabber.org/streams; xmlns=jabber:client (14:40:05) jabber: Recv (ssl)(197): stream:featuresmechanisms xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismX-OAUTH2/mechanismmechanismX-GOOGLE-TOKEN/mechanismmechanismPLAIN/mechanism/mechanisms/stream:features (14:40:05) sasl: Mechs found: X-OAUTH2 X-GOOGLE-TOKEN PLAIN (14:40:05) jabber: Sending (ssl) (***@google.com): auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga=' http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'password removed/auth (14:40:06) jabber: Recv (ssl)(77): failure xmlns=urn:ietf:params:xml:ns:xmpp-saslnot-authorized//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 *@google.com/(0x7fb13f83e180) (14:40:06) connection: Disconnecting connection 0x7fb140716080 (14:40:06) jabber: Sending (ssl) (@google.com): /stream:stream (14:40:06) connection: Destroying connection 0x7fb140716080 (14:40:06) util: Writing file prefs.xml to directory /home/***/.purple (14:40:06) util: Writing file /home/***/.purple/prefs.xml (14:40:06) util: Writing file accounts.xml to directory /home//.purple (14:40:06) util: Writing file /home//.purple/accounts.xml I also used the workaround contained here https://developer.pidgin.im/wiki/Protocol%20Specific%20Questions#WhydoIgetaServerdoesnotuseanysupportedauthenticationmethoderrorbut I didn't solve. 2013/3/21 Daniel Atallah datal...@pidgin.im On Thu, Mar 21, 2013 at 9:22 AM,
