That was it indeed. Thanks

mcaction — Wed, 11 Oct 2006 02:10:19 +0000

That was it indeed. Thanks so much.

ports 5222 and 5269 are being used

mfoss — Tue, 10 Oct 2006 08:01:22 +0000

mcaction wrote:

I'm using apache on this particular server and ip address which I guess is why it fails to open a socket. Also, I don't see any possibility of telling 'ejabberd_listener' not to use port 80. What are my options?

That 80 mentioned on the error message indicates the line number on the module. So that 80 has no relation to Apache, or port numbers.

Your problem is a conflict in port numbers 5222 and 5269, as explained on this FAQ entry. You have either ejabberd or another Jabber server already running on that machine.

ejabberd - Comments for "ejabberd conflicting on port 80 with existing apache instance"

That was it indeed. Thanks

ports 5222 and 5269 are being used