Prepare the intended public hostnames
List the canonical hostname and any alternate hostname that should redirect to it. HTTPS acceptance needs to cover the actual paths readers will use, not just a certificate status in a control panel. Follow the current Cloudways certificate instructions for the selected application. A successful certificate operation is relevant evidence, but it does not prove that DNS, redirects and every embedded resource are correctly configured.
Check content delivery as well as the connection
Load representative pages through the intended secure URL and inspect whether navigation, images and important functions use the expected destinations. A page can open over HTTPS while still containing outdated links or resource references from the previous environment. Do not broadly rewrite application data without understanding the scope. Record the exact mismatch and correct only the demonstrated issue using a tested procedure with an appropriate recovery path.
Verify both sides of the cutover
A fictional migration may pass a destination preview check and later fail on the public hostname because the routing or hostname configuration differs. Verify the relevant public behavior after the cutover as well as before it. Keep a distinction between what was observed locally, in preview and on the live canonical address. None of these observations should be presented as a guarantee about every future renewal or network condition.
Assign continuing ownership
Document who receives certificate or service notices and who can act if a hostname changes. Avoid an arrangement where the only knowledgeable operator leaves immediately after launch. The ongoing task is modest but important: keep the domain, routing and certificate responsibilities aligned. If a warning appears, preserve the exact message and affected hostname before changing settings; do not ask visitors to bypass a security warning as a normal operating procedure.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Cloudways custom-certificate deployment — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21
- Cloudways getting-started documentation — Merchant documentation · support.cloudways.com · Merchant-controlled · checked 2026-09-21