Secure Apache2 with Let’s Encrypt SSL on Debian 10/11


In the following post, we’re going to showcase the procedure how to Secure Apache2 with Let’s Encrypt SSL on Debian 10(this procedure works on Debian 11 as well). The post will showcase the scenario, where we need to install certbot on our Debian machine and obtain the SSL certificate from Let’s Encrypt, setup the automatic HTTPS redirection and test out the certificate renewal as well. Here we already have a Debian machine with Apache preinstalled on which we’re going to go through the steps on how to secure Apache2 with let’s encrypt ssl.


1. Registered and valid a domain name pointing to your Debian server.

2. Debian 10 server(or Debian 11)

3. Apache web server installed and running

4. Firewall configuration(open HTTP and HTTPS ports)

If you have UFW or IPTABLES firewall, you need to configure them to have them open ports 80 and 443 for HTTP and HTTPS in order not only to host your website


sudo ufw allow http
sudo ufw allow https


sudo iptables -I INPUT -p tcp -m tcp --dport 80 -j ACCEPT

sudo iptables -I INPUT -p tcp -m tcp --dport 443 -j ACCEPT


sudo iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT

sudo iptables -I INPUT -p tcp -m tcp --dport 443 -j ACCEPT

Secure Apache2 with Let’s Encrypt SSL on Debian

Certbot installation

We’ll be using the Let’s Encrypt tool Cerbot in order to obtain the SSL certificate and the Apache2 plugin for certbot as well. Both tools will help us to obtain the certificate very easily, quick and also make the necessary configuration changes on Apache2. On top of that, the tools have the automation features, so upon SSL expiry, they can renew and install the certificate again.

sudo apt install certbot python3-certbot-nginx

One note – before running the command, first it’s needed to in your nginx configuration file, write at the ServerName parameter the actual domain name you pointed to your server. Certbot will look in your server block configuration that parameter and create the let’s encrypt configuration files according that parameter. Example in a picture bellow:

sudo nano /etc/apache2/sites-available/000-default.conf

Secure Apache2 with Let’s Encrypt SSL

Acquire the SSL certificate from Let’s Encrypt

Once you have confirmed that ports on firewall are opened and you finished with the certbot installation. To acquire the SSL certificate from Let’s encrypt we just need to run on command:

sudo certbot --apache -d

Secure Apache2 with Let’s Encrypt SSL

When you run this command, the certbot wizard will start. If you’re running the cerbot the first time, it will first ask to provide an email address to use as a contact and to agree to the Let’s encrypt’s license terms.

After that, it will run the http challenge, obtain the certificate and at the end it will ask you do you want it to configure right away the https redirection, which is also a good option.

As soon as the redirection configuration is completed, the new domain with SSL certificate should work right away.

Setup and test the automatic renewal

Let’s encrypt certificates are by default vaild for three months and the cerbot’s automated renewal is configured to renews the certificate at least once, when the certificate has less than 30 days of validity. Once the the SSL certificate is acquired, valid and active, double if the certbot’s timer service is active and running and test the renewal process with dry run option:

sudo systemctl status certbot.timer

Secure Apache2 with Let’s Encrypt SSL

sudo certbot renew --dry-run

Check the Apache configuration

You can double check the Apache configuration if the cerbot has successfully written the config for ssl certificates and for HTTPS redirection. Cerbot will restart the Apache once it’f finished with config you should have your domain/website secured and running with the active SSL.

Secure Apache2 with Let’s Encrypt SSL


To summarize, we went through the steps how to secure Apache2 with Let’s Encrypt SSL on Debian 10 machine and on Debian 11 machine. We used let’s encrypt’s certbot tool for SSL certificate requests and it’s automatic renewal. Thankfully to certbot and it’s Apache plugin the process is really simple and straightforward and quick to complete. One suggestion on this is – it would be a good option to have a backup of let’s encrypt folder and to have it frequently backed up(as certbot itself has suggested). This is of course optional and it depends on how have you set the frequency of certificate renewals.

Let’s encrypt service, even though free and very popular among the tech world, it is a good option to secure some types of websites. Although, their free certificates are not recommended to use on e-commerce web sites for an example or any type of site that needs to pass and store very sensitive data(credit cards and similar). That’s why by default it’s recommended to have a short renewal time for SSL certificates.

Thank you for your time…