If you’re encountering an SSL issue where a domain (e.g. example.net) forwards to your main site (example.com) but displays the message “example.net doesn’t support a secure connection,” follow the steps below to resolve the issue. This guide is for Ecenica web hosting plans with cPanel.
Prerequisites:
- Domain Hosted Elsewhere: The domain (
example.net) is hosted by another provider and needs to be forwarded to your Ecenica-hosted site. - Domain Setup on an Ecenica Web Hosting Plan: The main site (
example.com) is set up on an Ecenica web hosting plan with cPanel.
1. Add a Domain Alias in cPanel
- In cPanel, add a domain alias for the forwarding domain (e.g.,
example.net) to point to your main domain (example.com). This allows SSL coverage for all associated domains under your Ecenica account. See our Add a Domain Alias in cPanel guide.
2. Set Up a Domain Redirect (301 Redirect)
- Set up a 301 redirect for
example.netto ensure visitors are securely redirected tohttps://example.com`. Use the **Redirects** feature in cPanel to forwardexample.net` to your main site, ensuring all traffic is directed to the secure, HTTPS version of your website. For more details, follow our Create a 301 Domain Redirect in cPanel guide.
3. Update Name Servers or Change DNS
- Recommended Method: Update the domain’s name servers (NS) to Ecenica’s. This will automatically handle SSL for your domain, ensuring it’s correctly secured under Ecenica’s SSL certificate.
- Alternatively, if you are unable to change the NS records, you can update the DNS by adding two A records in your remote DNS configuration to point both
www.example.netandexample.netto your Ecenica IP address. You can obtain the IP address from the Ecenica Dashboard > cPanel or contact us for assistance.
Why We Recommend Changing Name Servers
- Changing the name servers to Ecenica ensures SSL is handled automatically by Ecenica’s servers, eliminating the need to manually update A records if the server IP changes in the future. This method provides a more streamlined and future-proof solution.
Why the SSL Error Occurs
The error “example.net doesn’t support a secure connection” typically occurs when a domain does not have a valid SSL certificate installed. SSL (Secure Socket Layer) is a protocol used to secure communications between a user’s browser and the server. It ensures that the data exchanged is encrypted and secure.
Here’s why the error might occur in your case:
1. SSL Certificate Not Installed for the Forwarding Domain
When you have a domain (e.g., example.net) forwarding to another domain (e.g., example.com), the forwarding domain must have its own SSL certificate if it is accessed directly using `https://example.net`. Without this certificate, browsers will show a security warning or error when attempting to establish a secure connection.
2. Domain Not Properly Configured to Use the SSL of the Main Domain
Even though example.net might be set up to forward to example.com, this forwarding often uses an HTTP (non-secure) connection unless configured to use HTTPS explicitly. Without proper SSL handling, browsers may attempt to access the domain securely but fail because SSL isn’t set up for that domain.
3. Misconfigured DNS Records
If the DNS records for the forwarding domain (example.net) are not correctly configured to point to the correct Ecenica server or if the DNS settings are outdated, it can result in SSL issues. The DNS configuration may be missing the necessary A records or the domain may not resolve properly to Ecenica’s IP address, preventing the SSL certificate from being applied correctly.
