So, I've configured ejabberd, and it appears to be working.... partially. I'm able to log on through a client, create accounts, etc. Through Exodus and it's Jabber Browser, I'm able to verify that the admin capabilities are working. I'm also able to use ejabberdctl successfully. However.... I'm not able to connect to the web interface. When I attempt to connect using my local browser to the remote system, I simply get a "Cannot find server". When I'm actually on the server and attempt to connect, I get the following (where my domain name has been replaced by example.com):
=====================================
# lynx
Looking up example.com:5280
Making HTTP connection to example.com:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Retrying as HTTP0 request.
Looking up example.com:5280
Making HTTP connection to example.com:5280
Sending HTTP request.
HTTP request sent; waiting for response.
Alert!: Unexpected network read error; connection aborted.
Can't Access `http://example.com:5280/admin/'
Alert!: Unable to access document.
lynx: Can't access startfile
=====================================
Taking a look at the ejabberd.log file, I only see the following (repeated for each time I try to connect) (where the correct IP addresses have been replaced with x's):
=====================================
=INFO REPORT==== 2006-09-13 18:52:17 ===
I(<0.257.0>:ejabberd_listener:90): (#Port<0.311>) Accepted connection {{70,9,x,x},1473} -> {{209,59,x,x},5280}
=====================================
However, from the sasl.log file, I get the following:
=====================================
=CRASH REPORT==== 13-Sep-2006::18:52:17 ===
crasher:
pid: <0.257.0>
registered_name: []
error_info: {undef,[{ejabberd_http,
start,
[{gen_tcp,#Port<0.311>},[http_poll,web_admin]]},
{ejabberd_listener,accept,3},
{proc_lib,init_p,5}]}
initial_call: {ejabberd_listener,init,
[5280,ejabberd_http,[http_poll,web_admin]]}
ancestors: [ejabberd_listeners,ejabberd_sup,<0.36.0>]
messages: []
links: [#Port<0.311>,<0.203.0>,#Port<0.310>]
dictionary: []
trap_exit: false
status: running
heap_size: 233
stack_size: 21
reductions: 411
neighbours:
=SUPERVISOR REPORT==== 13-Sep-2006::18:52:17 ===
Supervisor: {local,ejabberd_listeners}
Context: child_terminated
Reason: {undef,[{ejabberd_http,
start,
[{gen_tcp,#Port<0.311>},[http_poll,web_admin]]},
{ejabberd_listener,accept,3},
{proc_lib,init_p,5}]}
Offender: [{pid,<0.257.0>},
{name,5280},
{mfa,{ejabberd_listener,
start,
[5280,ejabberd_http,[http_poll,web_admin]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=PROGRESS REPORT==== 13-Sep-2006::18:52:17 ===
supervisor: {local,ejabberd_listeners}
started: [{pid,<0.258.0>},
{name,5280},
{mfa,{ejabberd_listener,
start,
[5280,ejabberd_http,[http_poll,web_admin]]}},
{restart_type,transient},
{shutdown,brutal_kill},
{child_type,worker}]
=====================================
Which means very little to me because I've never had a reason to learn erlang. ;-)
This same problem was referenced here:
http://www.ejabberd.im/node/334#comment-1680
Any information or assistance would be greatly appreciated.
Thanks much!
BTW, I'm using ejabberd 1.1.1 and erlang 10B10.
You can ignore this...
So, I looked into enough erlang to figure out the problem. The "undef,[{ejabberd_http" gave me an indication to check my build. While I thought I instructed portage (I'm using Gentoo) to include "web" in the build, I must have been mistaken. Recompiling the software with the web use flag did the trick.
Sorry for the static in the forum! Hopefully my blunder will help someone in the future. ;-)
Thanks for a great package!
It surely help me. I'm
It surely help me.
I'm installing on Gentoo...and can not see the admin page...and found your thread...and the solution.
Thank you ! :D