i have correctly setup the ejabberd chat server. My problem is that i had to change host name in ejabberd.cfg because my server is hosted in office.example.com and the file only had example.com in the settings. After an update is stopped working and i went to check the file again and the office.example.com part was removed. There was only example.com. Is there a way to keep it permanently?
The thing is it should connect to office.example.com which is the server running nethserver and not example.com which is a different server. In the host name it defaults to example.com whenever i update/install/remove something and not to office.example.com.
If NethServer is also the DNS server of the network, the client should automatically find the server’s address through special pre-configured DNS records. Otherwise, specify the server address in the advanced options.
In the DNS module where it says DNS Servers it’s set to 8.8.8.8, in the Hosts there’s office.example.com and Server Alias is empty. Where are the advanced settings that it says? In the chat server module i can only enable or disable ejabber.
Oh, i don’t think that’s the problem as the configuration file changes from having the host set to office.example.com to example.com. Not 100% but pretty sure it has something to do with this.
Anything else left as per defaults.
LAN clients were able to chat.
For external xmpp (pidgin) client used same settings but adding the server address on pidgin’s Advanced tab (connect server), and configuring my router to forward xmpp ports to the server.
Also tried from mobile phone with Conversations xmpp client, configuring it with the server address (used Public IP address, as had no real domain prepared). External client was able to chat.
With a real domain you might need to configure DNS SRV records. I think @filippo_carletti and @tzar can help you better on that.
I get it but the problem is that example.com is a different server in a different place used to host the website. office.example.com leads to the server that has jabber so if the client uses example.com it will try to connect to a different server to no avail.
Also i used the commands to enable webadmin interface but i only get this written in the browser when i try to connect to it using LAN IP:
I’m using office.example.com in pidgin to connect to the server and not an IP address. If i change the config file from example.com to office.example.com it works perfectly. Even further now that i run the commands for enabling the webadmin interface the config file was again changed to use example.com instead of the office.example.com and pidgin fails to connect.
I really appreciate your time and sorry for asking so many questions but i can’t seem to fix it.