Enabling the cPanel HTTPS redirect without a redirect loop

Test the intended hostname directly over HTTPS first. Confirm certificate coverage and understand any Cloudflare or reverse-proxy TLS mode. Record existing application, .htaccess and CDN redirects before adding another layer.

1. Open Domains and locate the hostname. Review its Force HTTPS Redirect control where available.
2. If the control is unavailable, inspect certificate status and domain type. Aliases may not show an independent toggle, and some conditions require provider assistance.
3. Enable the redirect for the intended domain, then open its HTTP address in a private browser session.
4. Inspect the final HTTPS URL and test www and non-www variants according to the site’s canonical-domain design.
5. Check application forms, login and checkout. If a CDN also handles redirects, confirm each layer agrees that the visitor’s intended connection is HTTPS.

HTTP should reach the intended HTTPS page with a short, predictable redirect chain. A browser padlock alone does not prove assets are free of mixed content, so review the developer-console messages as well.

If the browser reports too many redirects, revert the most recent change and compare origin and proxy settings. Cloudflare Flexible mode can conflict with an origin that insists on HTTPS. Do not remove a valid certificate or disable security broadly to solve a redirect loop.

The redirect changes incoming navigation. Stored asset URLs and application settings may still use HTTP and need an application-aware update. Avoid blind database replacements that can corrupt structured settings.

• Getting a free HTTPS certificate for a cPanel website
• Retrying AutoSSL after fixing a certificate-validation problem
• Removing a cPanel redirect and checking for cached rules
• Creating a page or domain redirect in cPanel

• cPanel: Domains
• Cloudflare: Too Many Redirects