HTTPS Was Supposed To Fix Trust. My WordPress Blog Now Shows Console Errors About Blocked Content

httpsmixed-contentssl6 replies · 171 views · started
  1. im literally losing my mind here client called me upset because their browser shows console errors about blocked content on my WordPress blog since the HTTPS switch.

    I checked quickly and the stylesheet are requested with http:// URLs. Some come from teh database content, some I can't trace. I'd rather fix it properly at teh source than install another plugin. Any systematic approach u recommend? Happy to dig into code or teh database, I just need a sensible plan. pls help 🙏

    thinking

    15
  2. is TLS terminated at a load balancer or CDN in front of teh server? ??

    1 0 helpful
  3. oh ive been there lol open DevTools > Console, each mixed content warning names the exact insecure URL: Mixed Content: The page at 'https://...' was loaded over HTTPS, but requested an insecure resource 'http://...'. clolect those URLs; the domain and path usually tell you whether its theme code, uploaded content or a third-party embed. good luck man!

    2 2 helpful
  4. hmmm for WordPress, old URLs live in teh database. Use WP-CLI: wp search-replace 'http://example.com' 'https://example.com' --all-tables --dry-run, check the count, then run it without --dry-run. it handles serialized data safely, unlike a raw SQL replace. take a database backup first. fingers crossed 🤞

    1 2 helpful
  5. for a static portfolio, honestly a quick find-and-relpace in the source and a redeploy beats any clever header... keep it simple. idk maybe im wrong lol

    0 4 helpful

Reply to this topic

Sign in or create an account to reply.