Enable SSL on web hosting
On HolyCloud shared web hosting (cPanel / DirectAdmin style panel), enabling HTTPS is not done via SSH on a VPS: everything is managed from the client panel and SSL / AutoSSL tools. This guide covers the usual steps to secure sites in production.
Prerequisites
- Active web hosting offer (not a Linux VPS)
- Domain pointing to hosting (correct A or CNAME record)
- Panel access (link provided in the HolyCloud client area)
Important difference: on a VPS you would install Certbot manually. Here, the provider manages Let's Encrypt or a shared certificate via AutoSSL.
Step 1: verify the domain in the panel
- Log in to the client area HolyCloud.
- Open Web hosting → your plan → Access panel (cPanel or equivalent).
- Domains / Domain Setup section:
- Primary domain and aliases (www) must be listed.
- Document root must match your site folder (e.g. public_html).
If the domain was just added, wait for DNS propagation (a few minutes to 48 hours).
Step 2: enable AutoSSL / Let's Encrypt
In cPanel (labels may vary by version):
- SSL/TLS Status or SSL/TLS → Manage SSL sites.
- Select the domain and Run AutoSSL / Install for Let's Encrypt.
- Wait for Valid status or a green check.
Alternative: Let's Encrypt™ SSL in the SECURITY area → choose domain → Issue.
Verify in your browser:
https://www.votredomaine.fr
Click the padlock → certificate issued by Let's Encrypt (or panel provider).
Step 3: force HTTPS (redirect)
Panel « Force HTTPS » method
- Domains → Domains.
- Enable Force HTTPS Redirect for the domain.
.htaccess method (Apache)
In the site public_html, edit or create .htaccess:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
« Always Use HTTPS » method (Cloudflare or panel)
If you use a CDN, also enable Always Use HTTPS on the CDN side to avoid mixed redirect loops.
Step 4: internal links and CMS
- WordPress: set Site URL to
https://in Settings → General, or use an HTTPS migration plugin. - Check there is no mixed content (images over
http://) in the browser developer console.
Renewal and expiration
AutoSSL usually renews Let's Encrypt certificates automatically before expiry (90 days).
If you receive an « SSL expiring » email:
- Run AutoSSL manually again.
- Verify the domain still resolves to hosting.
- Remove old expired certificates in SSL/TLS → Manage SSL sites if the panel offers it.
Troubleshooting
| ---------- | -------- |
|---|---|
| Redirect loop | Double HTTPS rule (panel + .htaccess) — keep only one |
| Subdomain not covered | Add subdomain in Domains then rerun AutoSSL |
What this guide does not cover
- Certbot installation on a Linux VPS (see VPS documentation).
- Manual wildcard certificates (often paid or specific DNS challenge).
Need help?
Open a ticket from the client area with the domain name and a screenshot of the SSL/TLS Status page.