Hi,
I have successfully installed ejabberd on my server, shifted from openfire to ejabberd because of the capability of pre binding.
I can connect through Strophe successfully and also receiving notifications on my site through XMPP. I am using version 2.1.5 which has the Mod-Http-Pre-Bind feature already installed.
My http-bind is working correctly in apache through proxy pass, but the same is not working for Mod-Http-Pre-Bind. In the configuration its shows port 5288 as the port for pre bind, when i look at listening ports on ubuntu only ports 5280, 5222 are visible.
So whenever a prebind is done i get a 503 service not available error, is there a solution to this problem or is it a configuration issue.
Regards,
Sheldon
sdz007 wrote: I am using
I am using version 2.1.5 which has the Mod-Http-Pre-Bind feature already installed.
ejabberd 2.1.5 includes a small patch to allow easier installation of pre-bind modules. However, ejabberd 2.1.5 doesn't include any pre-bind feature itself, you still have to install the additional pre-bind module. Seehttps://support.process-one.net/browse/EJAB-1128
In the configuration its shows port 5288 as the port for pre bind, when i look at listening ports on ubuntu only ports 5280, 5222 are visible.
In ejabberd 2.1.5 source code I don't see anywhere any mention to the word: 5288