Skip to content

Instantly share code, notes, and snippets.

@theel0ja
Last active April 14, 2017 18:53
Show Gist options
  • Save theel0ja/67bf7dde5f34a09498a78abc2e25ac1b to your computer and use it in GitHub Desktop.
Save theel0ja/67bf7dde5f34a09498a78abc2e25ac1b to your computer and use it in GitHub Desktop.
Let's encrypt installation to nginx

Let's Encrypt for nginx

Tutorial for installing Let's Encrypt for nginx. Works also with reverse proxy like CloudFlare.

Tested with:

  • Ubuntu 16.04 Server 64-bit
  • Nginx 1.10.0
  • letsencrypt-auto

#Install letsencrypt-auto Use following command to install Let's Encrypt Client:

sudo apt-get install git
git clone https://github.com/letsencrypt/letsencrypt
cd letsencrypt
./letsencrypt-auto

When it's done, it may say this:

Installation succeeded.
No installers seem to be present and working on your system; fix that or try running certbot with the "certonly" command
root@kaffe:~/letsencrypt# 

Create Cert

Run following command every time that you want to create a certificate.

/root/.local/share/letsencrypt/bin/letsencrypt certonly --webroot --webroot-path /usr/share/nginx/html/ --renew-by-default --email [email protected] --text --agree-tos -d yourdomain.com -d www.yourdomain.com

Replace:

  • [email protected] with your email
  • yourdomain.com with your domain
  • /usr/share/nginx/html/ with your website root domain

Install Cert

If you get message like this, you've created your certificate successfully:

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at
   /etc/letsencrypt/live/yourdomain.com/fullchain.pem. Your
   cert will expire on 2016-10-17. To obtain a new or tweaked version
   of this certificate in the future, simply run letsencrypt-auto
   again. To non-interactively renew *all* of your certificates, run
   "letsencrypt-auto renew"
root@kaffe:~/letsencrypt# 

Your certificate's path is:

/etc/letsencrypt/live/yourdomain.com/fullchain.pem

And private key is in:

/etc/letsencrypt/live/yourdomain.com/privkey.pem

Forcing SSL

Go to the sites-available folder with this command:

cd /etc/nginx/sites-available

Then, open your Vhost.

nano [your conf file, e.g. yourdomain.com]

Add this line to vhost, if you want to force SSL:

return 301 https://$server_name$request_uri;

Installing Certificate

Open your Vhost if it's not opened yet (you can also use instead of nano some another text editor, like vim).

nano [your conf file, e.g. yourdomain.com]

Copy your existing VHost to end of the file.

Change 80 (HTTP port) to 443 (HTTPS port), you can use another port if you want, and add this to under listen 443:

ssl on;
ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

Now your VHost should be like this:

server {
    listen 80;
    listen [::]:80;

    root /your/website/root;
    index index.php index.html index.htm;

    server_name yourdomain.com;
    return 301 https://$server_name$request_uri;
    
    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

    location ~ /\.ht {
        deny all;
    }
}

server {
    listen 443;
    listen [::]:443;

   root /your/website/root;
    index index.php index.html index.htm;

    server_name yourdomain.com;
    
    ssl on;
    ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

    location ~ /\.ht {
        deny all;
    }
}

Restart SSL and test it!

Use following command to restart your nginx:

sudo service nginx restart

If you don't get any message of it, and https://yourdomain.com/ works, you are installed successfully Let's Encrypt certificate to your web server!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment