
How to Fix Mixed Content Warnings After Moving WordPress to HTTPS
Find insecure resource requests after a WordPress HTTPS move, protect your backup, fix stored URLs, and verify important pages in DevTools and with curl.
Stories and guides about https.
18 articles

Find insecure resource requests after a WordPress HTTPS move, protect your backup, fix stored URLs, and verify important pages in DevTools and with curl.

Flexible mode plus an origin HTTPS redirect causes many Cloudflare loops. Learn to switch to Full (strict), inspect every redirect layer and choose one clear HTTPS policy.

Six eMudhra TLS signing keys were compromised. Check those issuers and the broader emSign ECC Root CA - G3 trust-removal scope, including your origin and server tools.

Add nosniff, Referrer-Policy, Permissions-Policy and X-Frame-Options on Apache or Nginx, handle inheritance and iframe permissions, then verify real GET responses.

Let's Encrypt plans to validate from seven locations from 10 November 2026. Test your challenge path and fix geo blocks, WAF challenges and bad redirects.

Chrome asks visitors before loading any public HTTP page, even a redirect hop. Find every HTTP hop with curl and fix apex, www and forwarding domains.

Test TLS 1.3 safely, inspect the effective Apache or Nginx virtual host, verify the certificate separately and keep TLS 1.2 enabled.

Cloudflare explained its Radar redesign on 8 October. Use this 9 October guide to compare networks, check DNS and HTTP, and send a useful outage support ticket.

Force HTTPS with one clean 301 redirect in cPanel, .htaccess, Nginx or Cloudflare, update WordPress, add HSTS safely, and fix the redirect loop for good.
Explore hosting built for your next chapter.