Setting in step 4 to the following: s2s_use_starttls: optional Server, you will unfortunately need to change the s2s_use_starttls Note that if you'd like to be able to talk to contacts via the GMail XMPP To requests after running for a while: 0 4 * * * root /bin/systemctl restart rvice To restart ejabberd once a day to ensure it doesn't stop responding Optionally create a cronjob in /etc/cron.d/restart-ejabberd Iptables -A INPUT -p tcp -dport 5269 -j ACCEPT Iptables -A INPUT -p tcp -dport 5222 -j ACCEPT Restart the ejabberd daemon: systemctl restart rviceĬreate a new user account for yourself: ejabberdctl register me up the following ports on the server's firewall: iptables -A INPUT -p udp -dport 3478 -j ACCEPT Optionally disable non-essential modules by commenting them out under the modules: section of /etc/ejabberd/ejabberd.yml: # mod_avatar Improve the client-to-server and server-to-server TLS configuration: define_macro:Ĭreate the required dhparams.pem file: openssl dhparam -out /etc/ejabberd/dhparams.pem 2048 Permissions correctly: chown root:ejabberd /etc/ejabberd/ejabberd.pem Set the following in /etc/ejabberd/ejabberd.yml: acl:Ĭopy the SSL certificate into the /etc/ejabberd/ directory and set the 'admin' as the username for the administrative user: apt install ejabberd To solve the Pidgin 'Not authorized' connection problems. Installing ejabberd on Debian is pretty simple and I mostly followed the I wrote a cronjob to renew this certificate automatically using certbot. Into the file that ejabberd expects: cat /etc/letsencrypt/live//privkey.pem /etc/letsencrypt/live//fullchain.pem > ejabberd.pemĪnd then restart the service: systemctl restart rvice Once you have the cert, you can merge the private and public keys Then, shutdown your existing webserver if you have one running and requestĪ cert like this: certbot -duplicate certonly -apache -d -d The easiest way to get a certificate is to install certbot: apt install certbot python3-certbot-apache Then I went to get a free TLS certificate for the above. My personal domain is and so I created the following DNS Services, I decided to setup my own XMPP / Jabber server on a server

I hope this post helps someone else struggling to setup ejabberd on EC2 as I did.In order to get closer to my goal of reducing my dependence on centralized This was a lot of effort, but it probably would have been easier if I had been familiar with Erlang applications and SRV DNS settings. That did it! The node name was the same regardless of the hostname associated with the particular AMI instance. I made those changes, removed all the database files from /var/lib/ejabberd, and restarted ejabberd. I did this by modifying /etc/default/ejabberd adding the line:Įxport requires adding jabber as a host name inside /etc/hosts:ġ27.0.0.1 localhost.localdomain localhost jabber One solution I found is to explicitly set the node name.

The problem is that the hostname and therefore the node name changes everytime the AMI is relaunched which confuses ejabberd. It looked something like this: This node name is somehow linked to the Mnesia database stored as files within /var/lib/ejabberd. By default the node name was dynamically set based on the hostname for the machine. ,Īfter some googling, I found that ejabberd associates itself with an Erlang node name, a concept I don't really understand that well.

Next I edited the ejabberd config file, /etc/ejabberd/ejabberd.cfg, making an admin user and setting the hostname as : That was a correct assumption for the most part.įirst, I logged into the VM and installed ejabberd: I was a little nervous about working with a server built with Erlang since I knew nothing about it, but it was a reputable server and I was counting on not needing to have any Erlang knowledge to work with ejabberd. I chose to setup ejabberd since it was an easy to install via apt-get. It turned out to be harder that I expected to setup a Jabber (XMPP) server on an Ubuntu virtual machine ( ami-ce44a1a7) within Amazon EC2.

Ejabberd aws