I open new connection and send "hello" message, servers responds with:
<body xmlns='http://jabber.org/protocol/httpbind' sid='82a808b634a7acc6ad327d02bafcd07d97fdb640' wait='60' requests='2' inactivity='30' maxpause='120' polling='2' ver='1.6' from='*********' secure='true' authid='4186371204' xmlns:xmpp='urn:xmpp:xbosh' xmlns:stream='http://etherx.jabber.org/streams' xmpp:version='1.0'><stream:features xmlns:stream='http://etherx.jabber.org/streams'><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register xmlns='http://jabber.org/features/iq-register'/></stream:features></body>Then I try to login in with:
<body rid='1573741821' sid='82a808b634a7acc6ad327d02bafcd07d97fdb640' xmlns='http://jabber.org/protocol/httpbind'><iq type="set" id="1001"><query xmlns="jabber:iq:auth"><username>abcdef</username><password>abcdef</password><resource>abcdef</resource></query></iq></body>And server responds with:
<body xmlns='http://jabber.org/protocol/httpbind'><iq xmlns='jabber:client' from='***********88' id='1001' type='error'><error code='503' type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq></body>Any idea why it happens ?? (I'm using ejabberd-2.0.0-beta1)
jwchat configured on apache2 with ejabberd doesn't work
Hello, I want to use jwchat configured on apache2 with ejabberd. I am using the latest versions. But when I run the jwchat page, click the login button, jwchat window opens but then a message pops out with "service not available" message. When I type it is redirected to . This means apache2 is redirecting to http-bind of ejabberd. There is no error log in apache. Is this the problem of ejabberd.
Also if I use jwchat with the mod_http_fileserver feature of ejabberd, it is working fine.
My httpd.conf is like this
ServerName myserver.com
DocumentRoot /var/www/jwchat
Options +Indexes +MultiViews
AddDefaultCharset UTF-8
RewriteEngine On
RewriteRule http-bind/
Please help me. Its been 3 weeks I am working for this.
Regards,
Pratik
http-bind problem
I have problem with http_bind in ejabberd-2.0.0. When I try to create new BOSH session I see this in logs:
=CRASH REPORT==== 26-Feb-2008::21:35:32 ===crasher:
pid: <0.417.0>
registered_name: []
exception exit: {noproc,
{gen_server,call,
[ejabberd_http_bind_sup,
{start_child,
["50a3a68732f65748ef97efff49a1fd8ff71c3170",
[]]},
infinity]}}
in function gen_server:call/3
in call from ejabberd_http_bind:process_request/1
in call from ejabberd_http:process_request/1
in call from ejabberd_http:process_header/2
in call from ejabberd_http:receive_headers/1
initial call: ejabberd_http:receive_headers({state,gen_tcp,#Port<0.422>,
undefined,undefined,
undefined,undefined,
undefined,undefined,"en",
[{["admin"],
ejabberd_web_admin},
{["http-bind"],
mod_http_bind}],
false,[]})
ancestors: [ejabberd_http_sup,ejabberd_sup,<0.40.0>]
messages: []
links: [<0.260.0>,#Port<0.422>]
dictionary: []
trap_exit: false
status: running
heap_size: 2584
stack_size: 23
reductions: 1112
neighbours:
=SUPERVISOR REPORT==== 26-Feb-2008::21:35:32 ===
Supervisor: {local,ejabberd_http_sup}
Context: child_terminated
Reason: {noproc,
{gen_server,call,
[ejabberd_http_bind_sup,
{start_child,
["50a3a68732f65748ef97efff49a1fd8ff71c3170",[]]},
infinity]}}
Offender: [{pid,<0.417.0>},
{name,undefined},
{mfa,{ejabberd_http,start_link,
[{gen_tcp,#Port<0.422>},
[http_bind,web_admin]]}},
{restart_type,temporary},
{shutdown,brutal_kill},
{child_type,worker}]
solved
solved
What was your problem
What was your problem ?
--
Mickaël Rémond
fixing http_bind
Apparently you have to have mod_http_bind specified in your modules in order for it to work in ejabberd-2.0.0. I was having similar problem where ejabber would complain that noproc ejabberd_http_bind_sup which is started in mod_http_bind initialization which in turn never occurs if you don't add mod_http_bind into your modules. Haven't found it anywhere but after debugging for what was going wrong with it decided to try this guess and it worked! In case anybody has similar problem, make sure you have line: {mod_http_bind, []} in your modules.
yes, problem was in
yes, problem was in mod_http_bind's absent in modules section. I think it would be better to restrict answers from binding where it is not in the modules section to prevent such configuration mistakes.