#1831 jabber: BOSH: Received invalid XML / XML parser error
Reporter
Jon
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Type-Defect
Priority-Medium
Status-Invalid
Jon
on
Using prosody version 0.12.4 on ubuntu along with client pidgin windows version 2.14.2
Prosody CFG LUA configured for BOSH on 443
Symptom: Pidgin client partially connects. The Prosody shows the client attach, status messages states (away, available) update. Buddy list doesn't populate, unable to send or receive any messages.
Unable to determine if Prosody is sending an odd formatted XML of which the client is unable tp parse.
Prosody debut doesn't provide much.
Nov 23 09:19:21 connODLJf-raWh5u debug New connection FD 20 (172.17.0.2, 43084, 172.17.0.11, 443) on server FD 8 (*, 443)
Nov 23 09:19:21 connODLJf-raWh5u debug Starting TLS now
Nov 23 09:19:21 connODLJf-raWh5u debug TLS handshake complete (TLSv1.3 with TLS_AES_128_GCM_SHA256)
Nov 23 09:19:21 connODLJf-raWh5u debug Connected (FD 20 (172.17.0.2, 43084, 172.17.0.11, 443))
Nov 23 09:19:21 runneruqSeTxn806dg debug creating new coroutine
Nov 23 09:19:21 http.server debug Firing event: POST /http-bond
Nov 23 09:19:21 http.server debug Firing event: POST xmpp.abcdef.online/http-bond
Pidgin debug indicates: BOSH: Received invalid XML
(10:00:35) nss: Trusting CN=abcdomain.online
(10:00:35) certificate: Successfully verified certificate for xmpp.abcdomain.online
(10:00:35) jabber: bosh: httpconn 057B6178 re-connected
(10:00:35) jabber: SendBOSH Boot (ssl)(238): <body content='text/xml; charset=utf-8' secure='true' to='xmpp.abcdomain.online' xml:lang='en' xmpp:version='1.0' ver='1.6' xmlns:xmpp='urn:xmpp:xbosh' rid='256971049167646' wait='60' hold='1' xmlns='http://jabber.org/protocol/httpbind'/>
(10:00:36) xmlnode: XML parser error for xmlnode 05665EB8: Domain 1, code 4, level 3: Start tag expected, '<' not found
(10:00:36) jabber: RecvBOSH (ssl)(16): error code: 1033
(10:00:36) jabber: BOSH: Received invalid XML
(10:00:40) util: Writing file prefs.xml to directory C:\Users\abcdef\AppData\Roaming\.purple
(10:00:40) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\prefs.xml
(10:00:40) util: Writing file accounts.xml to directory C:\Users\abcdef\AppData\Roaming\.purple
(10:00:40) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\accounts.xml
(10:00:41) util: Writing file blist.xml to directory C:\Users\abcdef\AppData\Roaming\.purple
(10:00:41) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\blist.xml
Thanks for any insight
Jon
on
Was able to resolve this issue. Believe it was the pidgin client issue. Wish you could post screenshots.
Previously I was leaving the advanced tab, connect port at zero.
Within pidgin advanced tab the working configuration:
Connect port: 5281
Connect server: server.domain.ext
BOSH URL: https://server.domain.ext:5281/http-bind
The important bits from prosody.cfg.lua:
"http"; -- Enables mod_http
"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
https_ports = { 5281 }
https_interfaces = { "*", "::" }
Please close this issue.
Jon
on
Gary, Your are correct, type on Pidgin version, currently running 2.14.12.
Thanks for the help. Apologies for consuming your time with an end user configuration issue.
Zash
on
Sorry we didn't respond earlier. Glad it was resolved. Closing.
Using prosody version 0.12.4 on ubuntu along with client pidgin windows version 2.14.2 Prosody CFG LUA configured for BOSH on 443 Symptom: Pidgin client partially connects. The Prosody shows the client attach, status messages states (away, available) update. Buddy list doesn't populate, unable to send or receive any messages. Unable to determine if Prosody is sending an odd formatted XML of which the client is unable tp parse. Prosody debut doesn't provide much. Nov 23 09:19:21 connODLJf-raWh5u debug New connection FD 20 (172.17.0.2, 43084, 172.17.0.11, 443) on server FD 8 (*, 443) Nov 23 09:19:21 connODLJf-raWh5u debug Starting TLS now Nov 23 09:19:21 connODLJf-raWh5u debug TLS handshake complete (TLSv1.3 with TLS_AES_128_GCM_SHA256) Nov 23 09:19:21 connODLJf-raWh5u debug Connected (FD 20 (172.17.0.2, 43084, 172.17.0.11, 443)) Nov 23 09:19:21 runneruqSeTxn806dg debug creating new coroutine Nov 23 09:19:21 http.server debug Firing event: POST /http-bond Nov 23 09:19:21 http.server debug Firing event: POST xmpp.abcdef.online/http-bond Pidgin debug indicates: BOSH: Received invalid XML (10:00:35) nss: Trusting CN=abcdomain.online (10:00:35) certificate: Successfully verified certificate for xmpp.abcdomain.online (10:00:35) jabber: bosh: httpconn 057B6178 re-connected (10:00:35) jabber: SendBOSH Boot (ssl)(238): <body content='text/xml; charset=utf-8' secure='true' to='xmpp.abcdomain.online' xml:lang='en' xmpp:version='1.0' ver='1.6' xmlns:xmpp='urn:xmpp:xbosh' rid='256971049167646' wait='60' hold='1' xmlns='http://jabber.org/protocol/httpbind'/> (10:00:36) xmlnode: XML parser error for xmlnode 05665EB8: Domain 1, code 4, level 3: Start tag expected, '<' not found (10:00:36) jabber: RecvBOSH (ssl)(16): error code: 1033 (10:00:36) jabber: BOSH: Received invalid XML (10:00:40) util: Writing file prefs.xml to directory C:\Users\abcdef\AppData\Roaming\.purple (10:00:40) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\prefs.xml (10:00:40) util: Writing file accounts.xml to directory C:\Users\abcdef\AppData\Roaming\.purple (10:00:40) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\accounts.xml (10:00:41) util: Writing file blist.xml to directory C:\Users\abcdef\AppData\Roaming\.purple (10:00:41) util: Writing file C:\Users\abcdef\AppData\Roaming\.purple\blist.xml Thanks for any insight
Was able to resolve this issue. Believe it was the pidgin client issue. Wish you could post screenshots. Previously I was leaving the advanced tab, connect port at zero. Within pidgin advanced tab the working configuration: Connect port: 5281 Connect server: server.domain.ext BOSH URL: https://server.domain.ext:5281/http-bind The important bits from prosody.cfg.lua: "http"; -- Enables mod_http "bosh"; -- Enable BOSH clients, aka "Jabber over HTTP" https_ports = { 5281 } https_interfaces = { "*", "::" } Please close this issue.
Gary, Your are correct, type on Pidgin version, currently running 2.14.12. Thanks for the help. Apologies for consuming your time with an end user configuration issue.
Sorry we didn't respond earlier. Glad it was resolved. Closing.
Changes