Force HTTPS for a domain in cPanel
Redirect every visitor to HTTPS with the Force HTTPS Redirect toggle on the cPanel Domains page or an .htaccess rule, then avoid redirect loops and mixed content.
- Beginner
- Linux VPS
- 4 min read
Having a certificate is not enough: visitors who type http:// or follow old links still land on the insecure version. Forcing HTTPS sends every request to the secure address with a permanent redirect. This guide covers the one-click toggle in cPanel, the .htaccess method for more control, and the two problems people hit afterwards: redirect loops and mixed content.
RunRacks does not sell cPanel licences. You buy one from cPanel or a partner and install it on your RunRacks Linux VPS.
Before you start
- A cPanel login for the account.
- A valid certificate on the domain, and on
wwwif you use it. Check cPanel » Security » SSL/TLS Status. If it is missing, see set up AutoSSL in cPanel & WHM. - The site loading correctly at
https://example.combefore you force it.
Forcing HTTPS on a domain without a valid certificate sends every visitor to a browser security error. Fix the certificate first.
Option 1: the Force HTTPS Redirect toggle
- In cPanel, open Domains » Domains.
- Find the domain in the list.
- Switch on Force HTTPS Redirect.
cPanel adds the redirect at the web server level for that domain. The toggle is greyed out when the domain has no valid certificate, which protects you from the error above.
This is the simplest option and works for most sites. Repeat it for each addon domain or subdomain that needs it.
Option 2: an .htaccess redirect
Use .htaccess when you need more control, such as choosing between www and the bare domain in the same rule.
Open Files » File Manager, turn on Show Hidden Files (dotfiles) in Settings, then edit .htaccess in the domain's document root. Add this at the very top:
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]To force HTTPS and send everyone to www:
RewriteEngine On
RewriteCond %{HTTPS} !=on [OR]
RewriteCond %{HTTP_HOST} !^www\. [NC]
RewriteRule ^ https://www.example.com%{REQUEST_URI} [L,R=301]Test with a temporary R=302 first. Browsers cache 301 redirects hard, so a mistake with 301 can stick in your browser even after you fix it.
Use one method, not both. Two redirect systems for the same domain make loops more likely.
Check it works
From any computer:
curl -sI http://example.com | grep -iE '^(HTTP|location)'
curl -sI https://example.com | head -1The first command should show a 301 and a Location: starting with https://. The second should show 200 (or the expected redirect to www). Only one hop should happen; check with:
curl -sIL http://example.com | grep -iE '^(HTTP|location)'Fix redirect loops
"Too many redirects" usually means two layers disagree about whether the request is HTTPS:
- A CDN or proxy in front connects to the server over HTTP while the visitor uses HTTPS. The server keeps redirecting. Set the CDN to connect over HTTPS (full mode), or test the forwarded protocol header in your rule:
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]- The application redirects too. WordPress, for example, redirects to its Site Address. Make sure it is set to the
https://address, and thewwwchoice matches your redirect. - The toggle and an `.htaccess` rule both apply. Remove one.
Fix mixed content
After switching, a padlock warning usually means the page loads images, scripts or styles over http://. Open the browser developer console; it lists each insecure URL.
- In WordPress, update the site URLs to
https://and run a search-and-replace on the database for the oldhttp://example.comaddress. - In themes and custom code, change hard-coded
http://links tohttps://or relative paths. - External resources must support HTTPS. Replace any that do not.
Troubleshooting
- Toggle is greyed out: there is no valid certificate for the domain. Run AutoSSL and check its log.
- Redirect works for the domain but not `www`:
wwwhas no certificate or DNS record. Add it, run AutoSSL, then retest. - 500 error after editing `.htaccess`: a typo in the rule. Remove your lines, save, and add them again carefully.
- Old HTTP page still shows: the browser cached the earlier response. Test in a private window or with
curl.
Next steps
- Create other redirects: URL redirects in cPanel.
- Install a paid certificate if you need one: install a purchased SSL certificate.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Control panels
How to install Plesk on a Linux VPS (AlmaLinux and Ubuntu)
Install Plesk on a fresh Linux VPS with the official one-click installer, apply your licence key and log in to the panel for the first time on port 8443.
- Beginner
- Linux VPS
- 8 min read
Control panels
CyberPanel: back up and restore a website
Create on-demand and scheduled website backups in CyberPanel, download the archives off the server, and restore a site from a backup when something breaks.
- Intermediate
- Linux VPS
- 6 min read
Control panels
Plesk Backup Manager: schedule backups and restore a site
Set up scheduled backups in Plesk Backup Manager, keep a copy off the server, and restore a single domain or subscription when something goes wrong.
- Intermediate
- Linux VPS
- 7 min read