A page can load over HTTPS while still requesting old HTTP images, scripts or styles. The browser may block those requests or report an insecure page.

What to do

  1. Open browser developer tools and review the console for the exact HTTP asset URLs.
  2. Update the site configuration, content links or theme references to their valid HTTPS equivalents.
  3. For WordPress, back up the database before using an appropriate URL-replacement tool; do not run a blind text replacement on serialized database content.
  4. Clear relevant caches and test the affected pages, including forms and embedded content.

Good to know

A redirect alone does not repair every hardcoded asset URL. Ask for help if changing the application’s base URL could lock you out.

Related help

Reviewed October 18, 2026. Need help? Contact JIJ support.

Bu cavab sizə kömək etdi? 0 istifadəçi bunu faydalı hesab edir (0 səs)

Powered by WHMCompleteSolution