Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

WordPress SSL redirect loops: find which layer disagrees about HTTPS

Published August 2026 · 2 min read · Updated 2026-09-05

WordPress SSL redirect loops happen when WordPress, the web server, and a reverse proxy disagree about whether the original request was HTTPS. The loop is often two layers alternately forcing opposite URL/scheme assumptions, not a certificate problem.

Capture the redirect sequence

Follow the URL with curl or browser network tools and record every HTTP status and Location header. Test both http:// and https:// forms plus www/apex variants to see which component changes the URL.

Use a temporary browser profile when cached 301/HSTS behavior could obscure the current server response.

Check WordPress home and siteurl

Verify the stored WordPress Address and Site Address match the intended canonical HTTPS hostname. Hard-coded wp-config constants can override database values, so inspect both.

Search for plugins that enforce SSL or canonical hostnames before adding another redirect rule.

Teach WordPress about proxy HTTPS correctly

If TLS terminates at a trusted reverse proxy, the origin may receive HTTP. Configure the proxy/application so the original scheme is communicated and trusted only from that controlled proxy.

A generic trust of X-Forwarded-Proto from the public internet can create security issues.

Consolidate redirect ownership

Choose one clear web/proxy canonical redirect path, remove duplicate plugin rules, purge caches, and retest. After the loop is gone, verify mixed content and certificate hostname separately.

  • Record every redirect.
  • Verify home/siteurl.
  • Handle trusted proxy scheme.
  • Remove duplicated SSL redirect rules.

Next step

Trace WordPress, proxy and web-server scheme handling to stop HTTPS redirect loops without treating a valid certificate as the cause of every loop.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move