Running your Drupal websites and blogs over HTTPS is a good thing. Google and other search engine providers are ranking sites using SSL/TLS or HTTPS better than those that are not.
If you’re currently running your websites without HTTPS, it may be time to switch.
Even today, most website providers are making all their customers’ websites HTTPS compliant by default. So if you’re still running your Drupal websites or blogs not using HTTPS, then you’re probably doing it wrong.
This brief tutorial is going to show students and new users how to convert existing Drupal websites from HTTP to HTTPS easily without losing your audience.
When you’re done, all traffic to your sites will be redirected to the HTTPS version of your content.
To get started with migrating your Drupal sites to HTTPS, continue with the steps below:
Step 1: Setup Let’s Encrypt Free SSL / TLS
The first step going all HTTPS is obtaining SSL/TLS certificates for your domain or site. Since Let’s Encrypt is free, continue below to obtain your free certificates to use.
Before obtaining Let’s Encrypt certificates, make sure your Nginx configuration is setup correctly. for your site config file, make sure the ServerName is defined with both non-www and www subdomain.
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 free Let’s Encrypt SSL/TLS certificate for your site.
sudo certbot --nginx -m [email protected] -d example.com -d www.example.com
After running the above commands, you should get 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
You must
agree in order to register with the ACME server at
-------------------------------------------------------------------------------
(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 is it 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: Donating to EFF:
The highlighted code block should be added to your Nginx Drupal configuration file automatically by Let’s Encrypt certbot. 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
} # managed by Certbot
# Redirect non-https traffic to https
# if ($scheme != "https") {
# return 301
# } # managed by Certbot
}
Step 2: Change Drupal Site URL
After configuring Nginx to use HTTPS above, change Drupal site URL to use HTTPS. this can be done by editing settings.php file in your Drupal root directory.
sudo nano /var/www/html/example.com/sites/default/settings.php
Open 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="";
Save the file
Now you should be able to logon to Drupal admin dashboard via HTTPS.
Step 3: Install Secure Login Plugin
Finally, logon to Drupal dashboard and install 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 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 setup 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:
