Most GreenGeeks SSL failures fall into one of three groups: the certificate was never issued because domain validation failed, the certificate exists but the site is not serving it, or the certificate is fine but the page pulls in insecure resources. Sorting your problem into the right group takes a minute and saves you from changing settings that were never the cause.
Identify Which Failure You Have
Open your site in a browser and look at what the address bar and page actually show. The symptom points to the likely cause.
- Certificate warning, expired or mismatched name: the browser is not receiving a valid certificate for that hostname.
- Site loads over HTTP, or HTTPS refuses to connect: the certificate may be missing or not installed on the account.
- Padlock appears but the browser flags "not secure" or mixed content: the certificate is working, and the problem is inside the page.
- HTTPS works for
wwwbut fails for the bare domain, or the reverse: one hostname is missing from certificate coverage.
A quick check with an online certificate lookup or your browser's certificate viewer tells you the issuing authority and the names covered. If no certificate is returned at all, skip ahead to the issuance checks. If one is returned and the dates look valid, the problem is serving or page content.
Confirm Where Your Domain Actually Points
GreenGeeks issues Let's Encrypt certificates automatically for domains on your account, and the validation step depends on reaching the domain you added. If DNS does not point where GreenGeeks expects, validation cannot complete and no certificate is issued.
GreenGeeks states that its domain control validation uses DNS or HTTP verification and works for domains on GreenGeeks Anycast nameservers or on third-party nameservers with A records, including Cloudflare. That flexibility is useful, but it means a stale or partial DNS setup is a common culprit.
Check these records at your registrar or DNS provider:
- A record for the bare domain and for
www. If either points to an old host, a wrong IP, or nothing, the validation request never reaches the correct server. - AAAA records. A valid A record with a broken AAAA record can still cause trouble when validators prefer IPv6 and the IPv6 destination is unreachable. Cloudflare notes that HTTP verification is preferably done over IPv6, so an AAAA record that does not match the A record's location can fail validation.
- Nameservers. If you recently moved hosts or registrars, confirm the delegation actually changed. Partial propagation can produce intermittent failures.
- CAA records. If any exist, they must permit the certificate authority to issue for your domain. A restrictive CAA record blocks issuance even when everything else is correct.
If you use Cloudflare in a partial (CNAME) setup where the validation token is served from your origin, no HTTP-to-HTTPS redirect should occur on the /.well-known/* path. Cloudflare also warns that WAF rules, IP access rules, or Under Attack mode can block the certificate authority from reaching the validation URL.
Read the SSL Manager and Run an AutoSSL Check
Once DNS looks right, trigger a fresh validation attempt rather than waiting. From the SSL Manager in the GreenGeeks Dashboard, click "Run AutoSSL Check" to run a check across all domains on the hosting account. In cPanel, the SSL/TLS Status page has a "Run AutoSSL" button, and you can watch progress on the same page.
When the check finishes, read the result per domain:
- Issued or active: the certificate is installed. Move to the serving and content checks below.
- Validation failed: the certificate authority could not confirm control of the domain. The DNS and HTTP checks in this guide apply.
- Excluded from AutoSSL: the domain's toggle is off, so GreenGeeks is not managing its certificate and one would need to be installed manually.
If a domain fails, GreenGeeks retries validation daily until the certificate issues or the domain is excluded. A new domain added to the account usually completes validation within 5 to 10 minutes, so a failure that persists well beyond that window points to a real blocker rather than timing.
Why Let's Encrypt Validation Fails
AutoSSL commonly uses HTTP-01 validation, in which the certificate authority requests a token file at a path such as /.well-known/acme-challenge/ on your domain. Anything that prevents that request from reaching your account with the expected response causes a failure.
Redirects and Forced HTTPS
A force-HTTPS redirect in .htaccess that catches the validation request can cause the check to fail, because the validation itself runs over plain HTTP. If you have a blanket redirect rule, confirm it excludes the ACME challenge path.
Port 80 and Firewalls
For HTTP-01 challenges, Let's Encrypt must connect to the server over port 80, and a closed, redirected, or filtered port causes validation to fail. On a VPS or dedicated server, check that no firewall rule blocks inbound port 80.
Proxies, CDNs, and Stale Records
Failures often stem from mismatched DNS records, blocked ports, reverse proxy rules, expired account data, or incorrect webroot paths. Stale _acme-challenge TXT records from a previous or abandoned certificate order can also block validation, so clear any you did not create for the current request.
If DNSSEC is enabled but misconfigured, for example stale DS records at the registrar after a DNS provider change, the certificate authority cannot securely resolve the challenge record and validation fails. AutoSSL may also skip domains that resolve to an incorrect IP address, have incomplete DNS propagation, hit HTTP validation errors, or carry restrictive CAA records.
Repeated failed attempts can trigger Let's Encrypt issuance rate limits, so stop retrying blindly once you have found a likely cause and fix it first.
Serve the Certificate Correctly
If the SSL Manager shows a valid certificate but browsers still complain, confirm you are testing the exact hostname covered. A certificate for www.example.com does not automatically cover example.com unless both are included in coverage.
Visit the site over HTTPS directly and check for the padlock in the address bar. If the padlock appears for one hostname and not another, the uncovered hostname needs to be added to AutoSSL coverage or handled separately.
On GreenGeeks VPS or dedicated servers, AutoSSL is managed in WHM rather than the shared hosting dashboard. Log in to WHM, search for "Manage SSL," and open "Manage AutoSSL" to confirm the feature is enabled. If AutoSSL was never turned on for the server, certificates will not issue no matter what the domain settings look like.
Fix Mixed Content and WordPress URL Settings
A working certificate can still produce a "not secure" warning when the page loads images, scripts, or stylesheets over http://. This is mixed content, and it is a page problem rather than a certificate problem.
For WordPress sites, GreenGeeks recommends updating the site URLs directly in the MySQL database to include HTTPS, rather than using a plugin such as Really Simple SSL, to avoid the extra performance overhead. Check the siteurl and home values in the wp_options table and change any http:// entries to https://.
After the URL change, scan for remaining hard-coded http:// references in theme files, page content, widgets, and plugin settings. A browser developer console will list the blocked insecure requests, which is usually the fastest way to find what still needs updating.
Rule Out Browser and Local Causes
Before escalating, eliminate the simple explanations:
- Test in a private window or a different browser to rule out cached certificate state.
- Test from a different network, since some corporate networks intercept TLS.
- Confirm the system clock on your device is correct, because a wrong clock produces false expiry errors.
- Check that a local antivirus or proxy is not replacing certificates.
- Try a plain command-line request to the domain to see which certificate is actually served.
If the site loads correctly over HTTPS everywhere except one device, the problem is local.
What to Send GreenGeeks Support
If DNS is correct, port 80 is reachable, no redirect or proxy is blocking the challenge path, and AutoSSL still fails, support can investigate the account side. Send them:
- The exact domain and hostname showing the error, including
wwwversus bare domain. - A screenshot or copy of the SSL Manager status and any validation error text.
- The output of a DNS lookup for A, AAAA, and CAA records.
- Confirmation of whether a CDN or proxy sits in front of the site.
- The result and timestamp of your most recent AutoSSL run.
- Whether the account is shared hosting or VPS/dedicated, since AutoSSL is managed in different places.
Some fixes are outside GreenGeeks' control. If DNS points elsewhere, the correction belongs at your registrar or DNS provider. If a domain is excluded from AutoSSL, GreenGeeks does not manage its SSL, and a certificate must be installed manually.
Third-Party DNS and CDN Setups
Running DNS elsewhere is supported, but it shifts responsibility for the validation path to you. Keep A and AAAA records consistent, review CAA records whenever you change providers, and clear out old challenge records after a migration.
If you use Cloudflare or a similar proxy, confirm that security features are not intercepting validation requests and that redirect rules leave the ACME challenge path reachable over HTTP. These settings are the usual cause when the certificate issued once but fails to renew after a proxy change.
GreenGeeks SSL problems are almost always reachability problems rather than broken server TLS configuration, so start with where the domain points and whether the validation request can reach the account. Work through DNS, the AutoSSL result, and page content in that order, and only escalate once each layer checks out.


