ejabberd - Comments for "setting probleme"

Then the problem is not in

mfoss — Wed, 11 Mar 2009 16:50:35 +0000

Then the problem is not in ejabberd, because ejabberd works correctly WHEN it receives the connection attempt.

The problem is probably in your DNS configuration.

when i try to connect to the

delphes — Wed, 11 Mar 2009 14:02:33 +0000

thanks badlop to try to help me

when i try to connect to the WebAdmin on localhost there is info report in the ejabberd.log

=INFO REPORT==== 2009-03-11 13:56:16 ===
I(<0.262.0>:ejabberd_listener:116) : (#Port<0.406>) Accepted connection {{127,0,0,1},11118} -> {{127,0,0,1},5280}
=INFO REPORT==== 2009-03-11 13:56:16 ===
I(<0.255.0>:ejabberd_http:123) : started: {gen_tcp,#Port<0.406>}
=INFO REPORT==== 2009-03-11 13:56:16 ===
I(<0.262.0>:ejabberd_listener:116) : (#Port<0.411>) Accepted connection {{127,0,0,1},11119} -> {{127,0,0,1},5280}
=INFO REPORT==== 2009-03-11 13:56:16 ===
I(<0.255.0>:ejabberd_http:123) : started: {gen_tcp,#Port<0.411>} 

but not when i'm on another computer when i open example.com:5280 :(

So ejabberd is listening in

mfoss — Tue, 10 Mar 2009 00:30:23 +0000

So ejabberd is listening in all IP addresses. The DNS is correctly configured to direct XMPP queries to the machine.

But what about HTTP? Maybe your web browser does not know where to find HTTP server "example.com port 5280".

When you try to connect to the WebAdmin, if ejabberd receives a connection attempt, it will show a line in ejabberd.log. Probably when you open example.com:5280, ejabberd does not show any line because he doesn't receive the connection attempt.