[Pidgin] #14690: Pidgin cannot connect to SoapBox server, host-unknown stream error

Pidgin trac at pidgin.im
Mon Oct 24 14:18:30 EDT 2011


#14690: Pidgin cannot connect to SoapBox server, host-unknown stream error
----------------------------------------------+-----------------------------
 Reporter:  lpeabody                          |        Owner:           
     Type:  defect                            |       Status:  new      
Milestone:                                    |    Component:  libpurple
  Version:  2.10.0                            |   Resolution:           
 Keywords:  xmpp host-unknown soapbox-server  |  
----------------------------------------------+-----------------------------
Description changed by lpeabody:

Old description:

> Currently we're operating on SoapBox Server 2007.  I've done some
> googling and cannot find which XMPP standard it uses, so I'm assuming it
> was the standard set in 2004
> http://tools.ietf.org/html/rfc3920#section-4.
>
> I'm running Pidgin 2.1.  The server requires SSL to authenticate.  I've
> told Pidgin to use old-style SSL and to allow plaintext auth over
> unencrypted systems, and to connect on port 5223.  It seems to
> authenticate fine, but errors out with a host-unknown stream error.  Here
> is the log.
>
> (14:10:14) account: Connecting to account
> lpeabody at im.ccom.unh.edu/bluewhale.
> (14:10:14) connection: Connecting. gc = 0x7f07b4534c00
> (14:10:14) dnsquery: Performing DNS lookup for 192.168.2.39
> (14:10:14) dnsquery: IP resolved for 192.168.2.39
> (14:10:14) proxy: Attempting connection to 192.168.2.39
> (14:10:14) proxy: Connecting to 192.168.2.39:5223 with no proxy
> (14:10:14) proxy: Connection in progress
> (14:10:14) proxy: Connecting to 192.168.2.39:5223.
> (14:10:14) proxy: Connected to 192.168.2.39:5223.
> (14:10:14) nss: subject=CN=ccom.unh.edu issuer=CN=ccom.unh.edu
> (14:10:14) certificate/x509/tls_cached: Starting verify for 192.168.2.39
> (14:10:14) certificate/x509/tls_cached: Checking for cached cert...
> (14:10:14) certificate/x509/tls_cached: ...Found cached cert
> (14:10:14) nss/x509: Loading certificate from
> /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
> (14:10:14) certificate/x509/tls_cached: Peer cert matched cached
> (14:10:14) nss/x509: Exporting certificate to
> /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
> (14:10:14) util: Writing file
> /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
> (14:10:14) certificate: Successfully verified certificate for
> 192.168.2.39
> (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
> <?xml version='1.0' ?>
> (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
> <stream:stream to='im.ccom.unh.edu' xmlns='jabber:client'
> xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
> (14:10:14) jabber: Recv (ssl)(214): <stream:error
> xmlns:stream="urn:ietf:params:xml:ns:xmpp-streams"><host-unknown
> xmlns="urn:ietf:params:xml:ns:xmpp-streams" /><text
> xmlns="urn:ietf:params:xml:ns:xmpp-streams" xml:lang="en-
> US"></text></stream:error>
> (14:10:14) jabber: Expecting stream header, got error with xmlns
> urn:ietf:params:xml:ns:xmpp-streams
> (14:10:14) connection: Connection error on 0x7f07b4534c00 (reason: 3
> description: XMPP stream header missing)
> (14:10:14) jabber: Expecting stream header, got host-unknown with xmlns
> urn:ietf:params:xml:ns:xmpp-streams
> (14:10:14) jabber: Expecting stream header, got text with xmlns
> urn:ietf:params:xml:ns:xmpp-streams
> (14:10:14) jabber: Recv (ssl)(16): </stream:stream>
> (14:10:14) jabber: xmlParseChunk returned fatal 5
> (14:10:14) account: Disconnecting account
> lpeabody at im.ccom.unh.edu/bluewhale (0x7f07b37a5f10)
> (14:10:14) connection: Disconnecting connection 0x7f07b4534c00
> (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
> </stream:stream>
> (14:10:14) connection: Destroying connection 0x7f07b4534c00
>
> Now, following is the definition of the host-unknown stream error:
>
> <host-unknown/> -- the value of the 'to' attribute provided by the
>       initiating entity in the stream header does not correspond to a
>       hostname that is hosted by the server.
>
> To me that means the Domain field in the Pidgin settings needs to be set
> to the hostname of the server, which I have done.  So I'm a bit confused
> as to why this is erroring out.

New description:

 Currently we're operating on SoapBox Server 2007.  I've done some googling
 and cannot find which XMPP standard it uses, so I'm assuming it was the
 standard set in 2004 http://tools.ietf.org/html/rfc3920#section-4.

 I'm running Pidgin 2.1.  The server requires SSL to authenticate.  I've
 told Pidgin to use old-style SSL and to allow plaintext auth over
 unencrypted systems, and to connect on port 5223.  It seems to
 authenticate fine, but errors out with a host-unknown stream error.  Here
 is the log.


 {{{
 (14:10:14) account: Connecting to account
 lpeabody at im.ccom.unh.edu/bluewhale.
 (14:10:14) connection: Connecting. gc = 0x7f07b4534c00
 (14:10:14) dnsquery: Performing DNS lookup for 192.168.2.39
 (14:10:14) dnsquery: IP resolved for 192.168.2.39
 (14:10:14) proxy: Attempting connection to 192.168.2.39
 (14:10:14) proxy: Connecting to 192.168.2.39:5223 with no proxy
 (14:10:14) proxy: Connection in progress
 (14:10:14) proxy: Connecting to 192.168.2.39:5223.
 (14:10:14) proxy: Connected to 192.168.2.39:5223.
 (14:10:14) nss: subject=CN=ccom.unh.edu issuer=CN=ccom.unh.edu
 (14:10:14) certificate/x509/tls_cached: Starting verify for 192.168.2.39
 (14:10:14) certificate/x509/tls_cached: Checking for cached cert...
 (14:10:14) certificate/x509/tls_cached: ...Found cached cert
 (14:10:14) nss/x509: Loading certificate from
 /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
 (14:10:14) certificate/x509/tls_cached: Peer cert matched cached
 (14:10:14) nss/x509: Exporting certificate to
 /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
 (14:10:14) util: Writing file
 /home/lpeabody/.purple/certificates/x509/tls_peers/192.168.2.39
 (14:10:14) certificate: Successfully verified certificate for 192.168.2.39
 (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
 <?xml version='1.0' ?>
 (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
 <stream:stream to='im.ccom.unh.edu' xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
 (14:10:14) jabber: Recv (ssl)(214): <stream:error
 xmlns:stream="urn:ietf:params:xml:ns:xmpp-streams"><host-unknown
 xmlns="urn:ietf:params:xml:ns:xmpp-streams" /><text
 xmlns="urn:ietf:params:xml:ns:xmpp-streams" xml:lang="en-
 US"></text></stream:error>
 (14:10:14) jabber: Expecting stream header, got error with xmlns
 urn:ietf:params:xml:ns:xmpp-streams
 (14:10:14) connection: Connection error on 0x7f07b4534c00 (reason: 3
 description: XMPP stream header missing)
 (14:10:14) jabber: Expecting stream header, got host-unknown with xmlns
 urn:ietf:params:xml:ns:xmpp-streams
 (14:10:14) jabber: Expecting stream header, got text with xmlns
 urn:ietf:params:xml:ns:xmpp-streams
 (14:10:14) jabber: Recv (ssl)(16): </stream:stream>
 (14:10:14) jabber: xmlParseChunk returned fatal 5
 (14:10:14) account: Disconnecting account
 lpeabody at im.ccom.unh.edu/bluewhale (0x7f07b37a5f10)
 (14:10:14) connection: Disconnecting connection 0x7f07b4534c00
 (14:10:14) jabber: Sending (ssl) (lpeabody at im.ccom.unh.edu/bluewhale):
 </stream:stream>
 (14:10:14) connection: Destroying connection 0x7f07b4534c00
 }}}


 Now, following is the definition of the host-unknown stream error:


 {{{
 <host-unknown/> -- the value of the 'to' attribute provided by the
       initiating entity in the stream header does not correspond to a
       hostname that is hosted by the server.
 }}}


 To me that means the Domain field in the Pidgin settings needs to be set
 to the hostname of the server, which I have done.  So I'm a bit confused
 as to why this is erroring out.

--

-- 
Ticket URL: <http://developer.pidgin.im/ticket/14690#comment:1>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list