Activate WordPress redirection to the secure HTTPS protocol.
To enable secure communication on your web hosting using the HTTPS protocol and SSL certificate, you will first need to activate the DV SSL service.
Information about this service and activation can be found in the section
DV SSL for free.
After activating DV SSL, first verify that secure connection availability is functioning correctly.
You can check this by entering your domain with the protocol "https:// + domain" in your browser.
In such cases, WordPress may automatically redirect to the unsecured protocol "http:// + domain".
If HTTPS is unavailable, after a long load time, your browser will notify you that the site is unavailable or there's a connection error.
If the verification is successful, log in to the WordPress admin and go to "Settings -> General".
Next, the settings are very simple: just add the letter "s" to the protocol HTTP in the fields "WordPress Installation (URL)" and "Site Homepage (URL)":
Redirection to the HTTPS protocol to improve speed and optimize WordPress is also set using the "mod_rewrite" rules in the ".htaccess" file.
For this edit, we will need an FTP client – we recommend
FileZilla – and a text editor, such as
Notepad++, which is free.
We do not recommend editing the file using the available "Notepad," as saving might alter its format and encoding.The
".htaccess" file is located in the FTP account within the WordPress installation folder, typically in the
"/www/" directory.
Download the ".htaccess" file from the FTP account to your local disk and open it in "Notepad++" for editing:
From the article with examples
Redirection to HTTPS, choose the first example of
".htaccess" rules
"Example .htaccess file – redirect to a specific domain". In our case, we are running only one domain at www.forpsi-test.com.
The example rules provided are as follows:
RewriteEngine On RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteCond %{HTTPS} off [NC] RewriteRule (.*) https://www.domain-name.com%{REQUEST_URI} [L,R=301,QSA]
Copy the "mod_rewrite" rules for redirecting to HTTPS and place them at the top of the file above the line "# BEGIN WordPress". Replace the section "domain-name.com" with "forpsi-test.com", i.e., your domain.
In our case, with the domain www.forpsi-test.com, the updated ".htaccess" file will look as follows:
The highlighted line no. 3 contains the updated domain name for forpsi-test.com.
Save the file and upload the updated ".htaccess" file back to the FTP account, overwriting the original ".htaccess" file in the "/www" folder.
Afterwards, you can test again whether the automatic redirection to HTTPS occurs in the browser after entering the URL with the HTTP protocol. For our case, it would be "http://forpsi-test.com/". It should then redirect to "https://www.forpsi-test.com/".
For similar testing of configuration or content changes, we recommend using the "Incognito mode/window" in the browser to prevent cached data from being used.
If the pages are accessible via HTTPS but you see a notification in the browser near the "lock" icon that your page "is not fully secure", check your web content (WordPress) further according to the article Why isn't my site secured?