Setting the SRV records for the domain using Godaddy's DNS could take from 24 to 48 hours to propagate the changes among all the global DNS records so be patient. In the screenshto Target is the Fually qualified domain hostname for the jabber server. I'm using Godaddy 's DNS for my domain so here is a screenshot on the SRV records that needs to be configured on Godaddy: To login to you will need to use the admin username previously added in this mypasswd1Īnyways in the web interface there is not much of configuration options available for change. Create ejabberd necessery new user accountsĭebian:~# /usr/sbin/ejabberdctl register admin mypasswd1ĭebian:~# /usr/sbin/ejabberdctl register hipo mypasswd2ĭebian:~# /usr/sbin/ejabberdctl register newuser mypasswd3ĭebian:~# /usr/sbin/ejabberdctl register newuser1 mypasswd4Įjabberdctl ejabberd server client (frontend) has multiple other options and the manual is a good reading.Įjabberctl can be used also to delete some existent users, for example to delete the newuser1 just added above:ĭebian:~# /usr/sbin/ejabberdctl unregister newuser Įjabberd server offers a web interface listening on port 5280, to access the web interface right after it is installed I used URL: Restarting jabber server: ejabberd is not running. ![]() Of course if there is some specific file which stores iptables rules or some custom firewall these rules has to be added / modified to fit appropriate place or chain. sbin/iptables -A INPUT -p tcp -m tcp -dport 53873 -j ACCEPT sbin/iptables -A INPUT -p udp -m udp -dport 4369 -j ACCEPT ![]() sbin/iptables -A INPUT -p tcp -m tcp -dport 4369 -j ACCEPT sbin/iptables -A INPUT -p udp -m udp -dport 5280 -j ACCEPT sbin/iptables -A INPUT -p tcp -m tcp -dport 5280 -j ACCEPT sbin/iptables -A INPUT -p udp -m udp -dport 5269 -j ACCEPT ![]() sbin/iptables -A INPUT -p tcp -m tcp -dport 5269 -j ACCEPT sbin/iptables -A INPUT -p udp -m udp -dport 5223 -j ACCEPT sbin/iptables -A INPUT -p tcp -m tcp -dport 5223 -j ACCEPT sbin/iptables -A INPUT -p udp -m udp -dport 5222 -j ACCEPT sbin/iptables -A INPUT -p tcp -m tcp -dport 5222 -j ACCEPT sbin/iptables -A INPUT -p tcp -m tcp -dport 22 -j ACCEPT Add iptables ACCEPT traffic (allow) rules for ports which are used by Ejabberd The rest of the configurations in /etc/ejabberd/ejabberd.cfg can stay like it is, though it is interesting to read it carefully before continuing as, there are some config timings which might prevent the XMPP server from user brute force attacks as well as few other goodies like for example (ICQ, MSN, Yahoo etc.) protocol transports.ģ. Ĭ) default %% Hostname of to my real hostname: %% Remove the Access Control Lists before new ones are added. %%%% Remove the Access Control Lists before new ones are added.%%%%override_acls. ![]() Inside I changed the default settings for: Now as ejabberd is installed, some minor configuration is necessery before the server can be launched: The installation of Ejabberd is standard, e.g.: Here is the exact steps I followed to have installed and configured a running XMPP jabber server. Besides that ejabberd doesn't need Apache or MySQL and only depends on erlang programming language. The reasons I choose Ejabberd is has rich documentation, good community around the project and the project in general looks like one of the best free software jabber servers available presently. After some research of the jabber server softwares available, I decided to install Ejabberd I've recently installed a jabber server on one Debian Lenny server and hence decided to describe my installations steps hoping this would help ppl who would like to run their own jabber server on Debian.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |