Fix www SSL on SiteGround: when this repair path applies
Reissue or assign a certificate covering both hostnames and ensure DNS for www resolves to the site. Use these steps when root certificate works but www fails, but first run the embedded diagnostic so the TLS, certificate and HTTPS evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
SiteGround Site Tools for Domain/DNS, Security/SSL and Email configuration. For Fix www SSL on SiteGround, confirm the active nameservers and exact service owner before changing check www DNS. A DNS-looking screen at siteground has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix www SSL on SiteGround
Record the current public state for check www DNS, reissue certificate, test SNI/hostname. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Check www DNS — Verify check www DNS from the public Internet and compare it with the value the responsible provider says should be live.
- Reissue certificate — Test the hostname actually requested, its certificate dates and SAN coverage, and the TLS handshake. Root and www can serve different certificates.
- Test SNI/hostname — Verify test SNI/hostname from the public Internet and compare it with the value the responsible provider says should be live.
- Retest redirect — Follow every hop rather than checking only the final page. The conflicting rule is usually visible where the chain changes scheme, hostname or destination repeatedly.
Repair steps in siteground
Reissue or assign a certificate covering both hostnames and ensure DNS for www resolves to the site.
- 1. Check www DNS. After this step, check the public value tied to check www dns before changing another unrelated setting.
- 2. Reissue certificate. After this step, check the public value tied to reissue certificate before changing another unrelated setting.
- 3. Test SNI/hostname. After this step, check the public value tied to test sni/hostname before changing another unrelated setting.
- 4. Retest redirect. After this step, check the public value tied to retest redirect before changing another unrelated setting.
Why this order matters for siteground
The sequence begins with the provider/authority decision, then moves through check www DNS, reissue certificate, test SNI/hostname. That keeps the change scoped to the failed TLS, certificate and HTTPS path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix www SSL on SiteGround
HTTPS should complete for the exact hostname, the certificate should be valid for that hostname, and root/www should follow the intended canonical redirect without a TLS error. Compare the same check www DNS and reissue certificate evidence used before the change; a repair is complete when the public result agrees, not merely when the siteground interface reports that a save succeeded.
If siteground and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting check www DNS value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix www SSL on SiteGround should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.