If HTTPS stopped working after a domain move, the cause is usually one of a few common issues: the domain is still resolving to the old server, the SSL certificate is installed only on the previous hosting account, the new hosting plan does not yet have a valid certificate, or the website is loading mixed content and the browser is blocking secure elements. In most cases, the problem is not with HTTPS itself, but with DNS, domain pointing, or certificate setup after the transfer.
After a domain move, it is normal to see temporary warnings such as “Your connection is not private”, “SSL certificate not trusted”, or a redirect loop between HTTP and HTTPS. These errors usually appear while DNS records are propagating or when the new hosting service has not finished issuing and attaching the SSL certificate to the correct domain.
Why HTTPS can stop working after moving a domain
HTTPS depends on two things working together: the domain must point to the correct hosting account, and that hosting account must have a valid SSL certificate for the domain name. If either part is missing or misconfigured, secure browsing breaks.
Common causes
- DNS still points to the old server or to an incorrect IP address.
- The SSL certificate was not migrated or reissued for the new hosting environment.
- The domain is added as an alias or parked domain but not as the primary site in the control panel.
- AutoSSL, Let’s Encrypt, or certificate provisioning has not completed yet.
- WWW and non-WWW versions of the domain do not match the certificate names.
- Redirect rules are forcing HTTPS before the certificate is ready.
- Mixed content is being loaded from insecure URLs after the site move.
- Cached browser or CDN data is showing an older certificate or old site route.
First checks to perform after a domain move
Before changing settings, confirm that the domain is pointing to the new hosting account and that the new account is ready to serve SSL traffic.
1. Confirm DNS points to the correct server
Check the domain’s A record, AAAA record, and nameserver settings. If you recently changed hosting, the domain may still be resolving to the previous IP address. During propagation, some visitors may reach the new site while others still see the old one.
- Verify the A record matches the new server IP.
- Check the AAAA record if your hosting uses IPv6.
- Confirm the nameservers are correct if DNS is managed by the hosting platform.
- Make sure there are no conflicting DNS records left from the old host.
If the domain still points to the previous server, the SSL certificate on the new host will not be used, and browsers may show an error if the old server certificate no longer matches the domain.
2. Make sure the domain is added correctly in the control panel
In platforms such as Plesk or similar control panels, the domain must be added to the correct subscription or website space. If the domain is missing, added under the wrong account, or set as an alias incorrectly, SSL provisioning may fail.
- Confirm the domain is listed as the active website.
- Check whether the domain should be the primary domain or a domain alias.
- Ensure the document root points to the correct site files.
- Review whether any redirection rules were carried over from the old host.
3. Check SSL certificate status
If you use Let’s Encrypt, AutoSSL, or another automatic certificate service, verify that the certificate was issued successfully for all required hostnames. Certificates must cover the exact domain names users browse to, including www if that version is used.
- Check the certificate expiration date.
- Confirm the domain name on the certificate matches the website URL.
- Include both example.co.uk and www.example.co.uk if both are used.
- Check whether the certificate was issued after the DNS update completed.
How to fix HTTPS after moving a domain
Step 1: Wait for DNS propagation if the move was recent
If the domain move happened recently, DNS propagation may still be in progress. Even when the change is correct, some networks continue using cached DNS data for a period of time. This can make it look like HTTPS is broken when in fact the browser is reaching an older destination.
Typical signs of propagation-related issues:
- The site works from one device but not another.
- HTTPS works on mobile data but not on office Wi-Fi.
- Some visitors see the new site, while others see the old one.
- The certificate warning changes depending on the network used.
In this case, confirm the DNS settings are correct and allow time for propagation to complete.
Step 2: Reissue or reinstall the SSL certificate
After a domain transfer, the SSL certificate from the old server usually cannot be reused automatically. You may need to issue a new certificate on the new hosting account.
In a control panel like Plesk:
- Open the domain’s hosting settings.
- Go to the SSL/TLS or Let’s Encrypt section.
- Request a new certificate for the domain.
- Include all required hostnames, such as the www version.
- Confirm the certificate is assigned to the domain.
If the platform uses AutoSSL, check whether it completed successfully. If it failed, review the error message carefully. Common reasons include DNS not yet pointing to the server, domain validation failure, or an incorrect alias configuration.
Step 3: Ensure the web server is serving HTTPS for the correct site
If the certificate is installed but the wrong site responds to requests, the web server configuration may be pointing to the old document root or another virtual host. This can happen after manual migrations or when multiple domains are hosted on the same account.
Check the following:
- The domain is mapped to the correct site directory.
- The Apache or web server vhost configuration was updated after the move.
- The SSL certificate selected in the control panel matches the domain.
- The website is not being served by an old default host configuration.
Step 4: Review redirect rules
Forced HTTPS redirects are useful, but if they are enabled before SSL is ready, users may see errors or redirect loops. This often happens when .htaccess rules or control panel redirects were copied from the old host without checking the new certificate status.
Review any redirects configured for:
- HTTP to HTTPS
- non-WWW to WWW
- WWW to non-WWW
- old domain to new domain
Make sure only one canonical redirect path is active. For example, if you redirect to https://www.example.co.uk, the certificate must cover that hostname and the DNS must point there correctly.
Step 5: Fix mixed content on the website
Sometimes HTTPS itself is working, but the browser still marks the page as not fully secure because some files are loaded over HTTP. This is called mixed content and is common after a domain move, especially if the site database contains old absolute URLs.
Look for insecure references in:
- Images
- Stylesheets
- JavaScript files
- Embedded videos
- Fonts
- API endpoints
To resolve mixed content:
- Update old HTTP links to HTTPS.
- Replace hard-coded domain references in the database if needed.
- Check theme, plugin, or application settings for base URL values.
- Clear any application cache after updating URLs.
Step 6: Clear caches and test from different locations
After fixing DNS or SSL settings, clear cache at every layer that may store old information:
- Browser cache
- Application cache
- Server-side cache
- CDN cache
- DNS cache on your device
Then test the website from another browser, another device, and another network. This helps confirm whether the problem is still active or only cached locally.
How to check whether the certificate matches the domain
A very common cause of HTTPS errors after a domain move is a hostname mismatch. The certificate must match the exact name the visitor uses in the browser.
Check both versions of the domain
If your site can be opened as both example.co.uk and www.example.co.uk, both versions should be supported correctly. If only one is included in the certificate, the other may produce a warning.
Best practice is to choose one preferred version and redirect all traffic to it. This avoids confusion and reduces SSL problems.
Check the certificate chain
Even when the domain name is correct, browser errors can appear if the intermediate certificate chain is incomplete. This is less common on managed hosting platforms, but it can happen after manual installations or migrations.
If your hosting control panel offers a full certificate bundle, install it rather than only the leaf certificate. This improves compatibility with browsers and mobile devices.
Special cases after a domain transfer
When the domain was moved but hosting stayed the same
If only the registrar or DNS provider changed, the website files may not have moved. In this case, HTTPS problems often happen because the DNS change has not fully taken effect or the SSL certificate was tied to the previous setup. Reissue the certificate if needed and verify the DNS points to the same hosting server.
When the website moved to new hosting
If both the domain and hosting changed, the new server must be fully prepared before switching DNS. Ideally, the site should already be configured, the SSL certificate should be requested, and the final HTTPS redirect should be tested after the domain resolves to the new IP.
When a CDN is involved
If you use a CDN or reverse proxy, HTTPS may fail if the CDN certificate, origin certificate, or DNS record is not aligned. Make sure:
- The CDN is configured for the correct domain.
- The origin server accepts HTTPS connections.
- The certificate at the origin is valid if the CDN connects to it directly.
- The proxy settings are not forcing an invalid hostname.
Recommended order of troubleshooting
If HTTPS is not working after a domain move, follow this order to avoid changing the wrong setting first:
- Check the domain’s DNS records and confirm the correct IP address.
- Verify the domain is added properly in the hosting control panel.
- Confirm the SSL certificate exists and includes the correct hostnames.
- Check whether the web server is serving the intended site.
- Review HTTPS redirects and remove conflicting rules.
- Fix mixed content if the page loads but appears insecure.
- Clear cache and retest from different networks.
Examples of what the error usually means
“NET::ERR_CERT_COMMON_NAME_INVALID”
This usually means the certificate does not match the domain name being visited. Check whether the certificate includes the www version or the non-WWW version that the browser is opening.
“This site can’t provide a secure connection”
This may mean the server is not configured for SSL on that domain, the certificate is missing, or the HTTPS service is not responding correctly on the new host.
Redirect loop between HTTP and HTTPS
This often happens when a forced HTTPS redirect is active but the server or proxy is also redirecting in another direction. Review .htaccess rules, platform redirects, and CDN SSL mode settings.
Browser shows a secure lock, but page elements are blocked
This usually indicates mixed content. The main page is over HTTPS, but some assets are still requested over HTTP.
Best practices to prevent HTTPS issues during future domain moves
- Lower DNS TTL before migration if possible.
- Prepare the new hosting account and website files before changing DNS.
- Issue the SSL certificate on the new host after the domain is added.
- Test both HTTP and HTTPS before switching live traffic fully.
- Use one preferred domain version and redirect the other consistently.
- Check for mixed content immediately after the move.
- Keep a record of old and new DNS values for troubleshooting.
FAQ
How long does HTTPS break after a domain move?
It depends on DNS propagation, browser caching, and how quickly the new certificate is issued. In many cases it resolves within a few hours, but some changes can take longer to fully reflect worldwide.
Do I need a new SSL certificate after moving a domain?
Often, yes. If the domain moves to a new hosting account or server, the SSL certificate usually needs to be reissued or reinstalled on the new environment.
Why does HTTP work but HTTPS fails after the move?
HTTP may still load because the site is reachable, but HTTPS requires a valid certificate and correct SSL configuration. The domain can be accessible without being securely configured.
Why does HTTPS work on one device but not another?
This is often caused by DNS propagation, cached certificates, or local DNS cache. Different networks and devices may still see different destinations during the transition.
Can a wrong www redirect cause HTTPS errors?
Yes. If the site redirects to a hostname not included in the certificate, browsers will show an SSL warning. Make sure the redirect target matches the certificate name.
What should I check in Plesk first?
Start with the domain’s hosting settings, then verify the SSL/TLS certificate, confirm the domain is assigned to the correct subscription, and check the site’s redirect rules. If Let’s Encrypt is used, confirm that issuance completed successfully.
Conclusion
If HTTPS is not working after a domain move, the issue is usually caused by DNS still pointing to the old location, a missing or mismatched SSL certificate, incorrect domain mapping in the control panel, or mixed content left behind after migration. The most effective fix is to verify DNS first, then confirm the certificate and web server configuration on the new hosting account, and finally review redirects and cached content.
Once the domain resolves to the correct server and the certificate matches the hostname visitors use, HTTPS should begin working normally again. If the problem continues after these checks, the next step is to review the hosting logs and SSL provisioning status in the control panel for more specific errors.