The Problem
When I encountered a “Not Secure” warning with the web browser, with a crossed-out https:// protocol specifically when trying to access my website via https://www.raymendis.com, I noticed that the bare domain (https://raymendis.com) was still loading securely without any issues.
The Cause
After logging into my KeyHelp administration panel on my Debian VPS, I realized that KeyHelp treats the root domain and the www subdomain as two separate entries in the domain list. While I had already activated the Let’s Encrypt SSL certificate and HTTPS redirection for the root domain, the security settings for the www subdomain entry were completely unconfigured and blank. Because there was no certificate assigned to the www variant, the browser flagged it as insecure.
The Solution
To fix this, I manually enabled the Let’s Encrypt certificate for the specific subdomain entry inside KeyHelp using these steps:
- Located the Subdomain: In the KeyHelp Domains control panel overview, I found the
www.raymendis.comrow and clicked the Edit (pencil icon) on the far right. - Activated Let’s Encrypt: I went to the domain’s Security tab and selected the Let’s Encrypt certificate radio button.
- Enforced HTTPS: I checked the Enabled box under Enforce secure connection to ensure any regular HTTP traffic automatically upgrades to secure HTTPS.
- Saved the Changes: I clicked Save at the bottom of the page.
Within 1 to 2 minutes, KeyHelp automatically provisioned the new certificate and reloaded my web server. Both my root domain and the www subdomain now show the green HTTPS badge in KeyHelp and load perfectly in the browser without any warnings.
