Help & Troubleshooting
HTTP/HTTPS Connectivity
What this is
This check connects to your site over both HTTPS and plain HTTP, verifying that HTTPS answers and that HTTP redirects visitors to the secure site rather than serving content (or nothing) in the clear.
How to read your result
Healthy: HTTPS responds (2xx/3xx) and HTTP answers with a 301 redirect to the https:// URL. HTTP timing out entirely is acceptable but loses visitors who type the bare address.
Common problems and how to fix them
HTTP serves the site without redirecting
How it shows up: Visitors who type the domain or follow old http:// links browse unencrypted; search engines may index both variants.
How to fix it: Add a permanent (301) redirect from http:// to https:// at the server or CDN — a one-line change in most configurations — and pair it with HSTS.
HTTPS not responding
How it shows up: The site is effectively down for modern users and browsers.
How to fix it: Check certificate validity, that the server listens on 443, and that firewalls/security groups permit it. If the certificate expired, renew it and fix the automation that should have renewed it.
Redirect loop or redirect to the wrong host
How it shows up: Browsers show "too many redirects", or visitors end up on an unexpected domain.
How to fix it: A common cause is a CDN and origin both redirecting each other (e.g. flexible-SSL setups). Set the origin to accept HTTPS from the CDN, and make each layer redirect only http→https, never the reverse.