What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
First identify where HTTPS fails: certificate issuance, certificate trust or hostname coverage, page content, or the redirect. These are different problems and need different fixes. Record the exact browser error and test the actual domain name—including both the apex domain and www if you use them—not just the server IP.
Start by identifying the failure
“SSL not working” can mean an AutoSSL certificate will not issue or renew, a browser rejects the certificate, a page loads but is marked insecure, or visitors are not redirected to HTTPS. Note which of these occurs and the exact browser message. Also check whether the problem affects the apex domain, www, an addon domain, or a subdomain; each name needs appropriate DNS routing and certificate coverage.
Test the intended hostname in the browser. A direct-IP visit can fail certificate verification because the certificate may not be issued for that IP. A warning on the domain itself can indicate a self-signed certificate or a certificate whose names do not match the requested hostname. cPanel describes these cases in its SSL verification error guidance.
Recommended Free Tools
If AutoSSL will not issue or renew
Check where the domain resolves
For the cPanel scenario, the hostname must resolve to an IP address on the server assigned to the cPanel account. Check the applicable A and AAAA records, and make changes at the DNS provider that actually hosts the domain’s authoritative zone. Do not assume the zone is managed in cPanel.
#1 Best Overall
Use the hosting account’s AutoSSL log to identify the failed validation. A missing resolution or a validation file returning 404 can occur when the domain points to an IP that is not on the server, but a 404 by itself does not prove DNS is the cause. Ehsan Dowlatshah, author of cPanel’s January 23, 2026 article, explains: “This means AutoSSL has problems resolving a domain to an IP address, either because the domain is not resolving to any IP address or is resolving to an IP address that is not bound to the server.” See cPanel’s AutoSSL DNS-resolution troubleshooting.
Understand the validation method
HTTP domain-control validation (DCV) fetches a temporary validation file from the website. DNS DCV adds a record to the domain’s DNS zone. Either method can validate a domain when it succeeds. If your DNS zone is hosted outside the cPanel/WHM server, cPanel’s DNS DCV cannot change that external zone; use a validation route your provider supports or ask the provider to configure it. cPanel explains the distinction in its guide to HTTP DCV and DNS DCV.
Rank #2
If HTTPS loads with a certificate warning
Separate a trust problem from a name mismatch. A self-signed certificate does not have the CA trust validation browsers expect. A hostname mismatch means the certificate does not cover the name being visited. Ask the host to verify the certificate’s domain coverage and which certificate and virtual host the server is presenting. Do not advise visitors to click through a warning on a public site.
In shared hosting, the customer may not have access to the server configuration needed to correct certificate selection or virtual-host problems. If the certificate appears valid in the control panel but the browser still rejects it, escalate with the exact hostname and browser error rather than repeatedly reinstalling it.
If the certificate is valid but the page looks insecure
A valid certificate secures the connection, but it does not automatically rewrite URLs embedded in the site. The browser may report mixed content when a page served over HTTPS requests resources over HTTP. Inspect images, scripts, stylesheets, fonts, embeds, and form actions for http:// URLs. Update the relevant site or CMS URLs to HTTPS, then retest the page. This is a page-content issue, not a certificate-issuance failure; cPanel outlines it in its mixed-content troubleshooting article.
If visitors are not redirected to HTTPS
A redirect does not create or repair a certificate. Confirm that HTTPS works with valid coverage first, then configure the redirect. In cPanel, the redirect control requires a valid certificate. For addon domains, the associated subdomain may also need its redirect toggle enabled; aliases do not show the toggle.
Rank #4
WordPress or another CMS may have its own redirect rules that conflict with the cPanel setting. If the control is unavailable or you encounter a redirect loop, review the CMS and server redirect configuration. cPanel’s instructions for automatically redirecting a domain to HTTPS are specific to cPanel; other shared-hosting panels may work differently.
What to send your hosting provider
Shared-hosting customers generally cannot change WHM or Apache virtual-host configuration. If DNS and site-level checks do not explain the problem, give support enough detail to investigate the server-side setup:
- The affected hostname or hostnames, and whether apex,
www, addon domains, or subdomains behave differently. - The exact browser error and the time you tested.
- The relevant A and AAAA record destinations and where the DNS zone is hosted.
- The cPanel SSL/TLS Status result and relevant AutoSSL log output, if available.
Ask the provider to check AutoSSL eligibility and provider configuration, domain-to-account IP binding, certificate coverage, certificate/key pairing, and which certificate and virtual host the server presents. cPanel documents additional checks in its SSL troubleshooting guide and AutoSSL management documentation. These cPanel-specific paths may not exist in another hosting panel, and the host may need to perform the checks.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
