🔐Free Native SSL via Let's Encrypt

Before you begin, make sure Port 443 is open and unblocked by any other application, firewall, or SELinux policies on your server.

This will enable HTTPS:// for your ESP, and also replace your Transactional SMTP Relay self-signed certificate with a real certificate so TLS will work with all SMTP Relay connecting applications.

Instructions for automating the renewal of your Let's Encrypt certificate every 30 days are at the end of this document, this is a one-time "set it and forget it" process.

Log into your VPS using SSH on macOS or PuTTY on Windows

ssh [email protected]

*** Note: Use the the real IP address of your VPS above, not 1.2.3.4, this is just a placeholder.

Change directory to your ESP installation:

cd edcom-install

You must be on the latest build for Let's Encrypt to work:

./upgrade.sh

Run this command and provide your ESP subdomain and domain as an argument.

./generate_letsencrypt_certificate.sh esp.yourdomain.com

*** Note: Use the the real subdomain and domain of your VPS above, not esp.yourdomain.com, this is just a placeholder. This is the domain you use to access your ESP with http:// currently.

Convert your ESP to use HTTPS:// from now on:

./convert_to_ssl.sh

Restart your ESP:

./restart.sh

Create an automated cron job that renews your Let's Encrypt certificate every 30 days.

Run the following command and when you're asked which editor to use, select nano:

crontab -e

Copy and paste the following into the bottom of the editor, change the placeholder domain to your real ESP domain, and hit ctrl-x to save:

* * */30 * * cd /root/edcom-install && ./renew_letsencrypt_certificate.sh esp.yourdomain.com > data/logs/certbot.log 2>&1

*** Note: Use the the real subdomain and domain of your VPS above, not esp.yourdomain.com, this is just a placeholder. This is the domain you use to access your ESP with http:// currently.

*** Note: If your ESP is installed somewhere else other than /root/edcom-install you will need to modify that as well.

You're done! Access your ESP using https:// from now on, and use https:// for all related configuration, such as the mta.conf file, API connections, Pabbly integrations, etc.