Hi. So I have ejabberd set up and configured and it's working pretty well. I do, however, have one odd issue that I was hoping to get some assistance with...
I can access everything from inside my network, chat, http-bind, admin, files transfer, etc....
For some reason, I cannot access jabber when connected outside of my network. Even more odd, I *CAN* access jabber when I'm on 4G (i.e., through my phone).
I use dyn.org to redirect traffic to my site, but I do not have a specific subdomain/webhop for jabber (i.e., jabber.mysite.com). I can access the site well using just the domain name.
At this point, I'm not sure if my issue is with ejabberd or dyn.org. Any thoughts on how to allow access to the outside world?
Running Ubuntu 16.04, ejabberd, apache2.
Update: So it turns out that it's not my setup, but rather my firewall at work, which still doesn't make any sense to me.
I can access chat only on port 5223. Nothing else works, including http-bind, webadmin, and file upload.
So my new question is, is there a work around for this? Perhaps I can use an alternate port?
In the original Jabber, port
In the original Jabber, port 5222 was for unencrypted client connections, 5223 for encrypted connections. It makes sense that your firewall allows 5223 but denies the others. Now you should find how to open the ports you want to use.
> Perhaps I can use an alternate port?
In ejabberd.yml you can change the port numbers as you want. For example, change 5222 to 5223. Of course then your clients have to connect to 5223. Or you can change 5280 to 80, etc.