I have configured a local ejabberd server on an Ubuntu box, and all seems to be going swell. s2s works for chatting and such, but s2s service discovery to my box from another server seems to not work as well as I'd hope.
I want to use the local server as a transport for the Jabber Mail component (which I already have working if I connect to the transport directly).
This screenshot pretty much explains my situation...
The bottom right pic is when you do a service discovery when connected directly to the server, whereas the top left pic shows what a service discovery looks like from another server to my local one (in this case from jabber.org.au).
Any helps is greatly appreciated :D
- Glenn
Re: Remote Service Discovery Configuration
I have configured a local ejabberd server on an Ubuntu box, and all seems to be going swell. s2s works for chatting and such, but s2s service discovery to my box from another server seems to not work as well as I'd hope.
This screenshot pretty much explains my situation...
I see you use Dyndns like me. You need to make sure that all the sub domains are resolvable from the Internet. You can do this by enabling an option in your Dyndns.org account to make all sub domains resolvable. It is called wildcard AFAIR. After you did that you can ask someone not in your LAN to ping "randomsubdomain.cradle.dyndns.org" if he gets your IP, it should work! :-)
Re: Remote Service Discovery Configuration
After you did that you can ask someone not in your LAN to ping "randomsubdomain.cradle.dyndns.org" if he gets your IP, it should work! :-)
And work it did!
I've enabled wild cards, and it now does resolve correctly from non-lan computers. Thank you heaps for the help, I have no idea how long it would have taken me to realise that oversight!
I had to restart pretty much everything, or maybe I just had to wait for the dns changes to roll out, either way it's working now.
Thanks for the help Sander :) It's a bit slow, but it seems to be working now, thanks a bunch!
A happy ejabberd user,
- Glenn