How to switch to HTTPS on Drupal with Nginx on Ubuntu Linux

|

,

|

This content provides a guide on how to convert Drupal websites from HTTP to HTTPS to improve rankings on search engines. The process entails setting up free SSL / TLS certificates using Let’s Encrypt, configuring the Nginx site for HTTPS usage, changing the Drupal site URL to use HTTPS and installing a Secure Login plugin…

This article explains switching to HTTPS with Drupal CMS on Ubuntu Linux.

There are several reasons why it’s a good idea to switch to HTTPS in Drupal CMS. First and foremost, HTTPS provides a secure connection between the user’s browser and your website, which helps to protect sensitive data such as login credentials and credit card information.

Additionally, HTTPS is becoming increasingly important for SEO purposes, as search engines like Google have started to prefer sites that use HTTPS over those that don’t.

Finally, with the rise of privacy concerns and data breaches, using HTTPS can help to build trust with your users and demonstrate that you take their privacy and security seriously.

Setup Let’s Encrypt Free SSL / TLS

The first step in all HTTPS is obtaining SSL/TLS certificates for your domain or site. Since Let’s Encrypt is free, continue below to receive free certificates.

Before obtaining Let’s Encrypt certificates, ensure your Nginx configuration is set up correctly. For example, provide the ServerName defined with non-www and www subdomains for your site config file.

server {
    listen 80;
    listen [::]:80;
    root /var/www/html/drupal;
    index  index.php index.html index.htm;
    server_name  example.com www.example.com;
.
.

When those settings are confirmed, continue below to get the certificate for your domain name.

To get the Let’s Encrypt SSL/TLS client installed on Ubuntu, run the commands below

sudo add-apt-repository ppa:certbot/certbot
sudo apt-get update
sudo apt-get install python-certbot-nginx

After that, run the commands below to obtain your site’s free Let’s Encrypt SSL/TLS certificate.

sudo certbot --nginx -m admin@example.com -d example.com -d www.example.com

After running the above commands, you should be prompted to accept the licensing terms. If everything is checked, the client should automatically install the free SSL/TLS certificate and configure the Nginx site to use the certs.

Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v01.api.letsencrypt.org/directory
-------------------------------------------------------------------------------
(A)gree/(C)ancel: A

Choose Yes ( Y ) to share your email address.

Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let's Encrypt project and the non-profit
organization that develops Certbot? We'd like to send you email about EFF and
our work to encrypt the web, protect its users and defend digital rights.
-------------------------------------------------------------------------------
(Y)es/(N)o: Y

This is how easy it is to obtain your free SSL/TLS certificate for your Nginx-powered website.

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
-------------------------------------------------------------------------------
1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you're confident your site works on HTTPS. You can undo this
change by editing your web server's configuration.
-------------------------------------------------------------------------------
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2

Pick option 2 to redirect all traffic over HTTPS. This is important!

After that, the SSL client should install the cert and configure your website to redirect all traffic over HTTPS.

Congratulations! You have successfully enabled https://example.com and
https://www.example.com

You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=example.com
https://www.ssllabs.com/ssltest/analyze.html?d=www.example.com
-------------------------------------------------------------------------------

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/example.com/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/example.com/privkey.pem
   Your cert will expire on 2018-02-24. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot again
   with the "certonly" option. To non-interactively renew *all* of
   your certificates, run "certbot renew"
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

The highlighted code block should automatically be added to your Nginx Drupal configuration file by Let’s Encrypt certbot. After that, your Drupal site is ready to be used over HTTPS.

server {
    listen 80;
    listen [::]:80;
    root /var/www/html/drupal;
    index  index.php index.html index.htm;
    server_name  example.com www.example.com;

    location / {
    try_files $uri /index.php?$query_string;        
    }

    location @rewrite {
               rewrite ^/(.*)$ /index.php?q=$1;
        }

    location ~ [^/]\.php(/|$) {
    fastcgi_split_path_info  ^(.+?\.php)(|/.*)$;
    fastcgi_index            index.php;
  # fastcgi_pass             unix:/var/run/php/php7.0-fpm.sock; # for Ubuntu 17.04
    fastcgi_pass             unix:/var/run/php/php7.1-fpm.sock; # for Ubuntu 17.10
    include                  fastcgi_params;
    fastcgi_param   PATH_INFO       $fastcgi_path_info;
    fastcgi_param   SCRIPT_FILENAME $document_root$fastcgi_script_name;
    }

    location ~ ^/sites/.*/files/styles/ { # For Drupal >= 7
               try_files $uri @rewrite;
        }

    location ~ ^(/[a-z\-]+)?/system/files/ { # For Drupal >= 7
        try_files $uri /index.php?$query_string;
        }

    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    if ($scheme != "https") {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    # Redirect non-https traffic to https
    # if ($scheme != "https") {
    #     return 301 https://$host$request_uri;
    # } # managed by Certbot

}

Change the Drupal Site URL

After configuring Nginx to use HTTPS above, change the Drupal site URL to HTTPS. This can be done by editing the settings.php file in your Drupal root directory.

sudo nano /var/www/html/example.com/sites/default/settings.php

Open the Drupal settings.php file in your Drupal root directory and add the lines below:

?php 

//Use HTTPS for Drupal
$_SERVER['HTTPS'] = 'on';
$conf['https'] = TRUE;
$base_url = 'https://example.com';

Save the file

Now, you can log on to the Drupal admin dashboard via HTTPS.

Install Secure Login Plugin

Finally, log in to the Drupal dashboard and install the Secure Login plugin to redirect all HTTP references to HTTPS.

After installing and activating the plugin, go to Configuration –> Secure Login. Then, check the box to redirect all pages to the secure URL. Including all forms

This should do it.

After that, your site should be HTTPS compliant.

Congratulations! You’ve successfully converted from HTTP to HTTPS

To set up a process to automatically renew the certificates, add a cron job to execute the renewal process.

sudo crontab -e

Then add the line below and save.

0 1 * * * /usr/bin/certbot renew & > /dev/null

The cron job will attempt to renew 30 days before expiring

You may also like the post below:

Like this:



Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.