Mixed content warnings after forcing HTTPS
After forcing HTTPS, pages still load http images, CSS, scripts or forms, so browsers show insecure-content warnings.
8 public reports
What's going wrong
Many owners who enabled forced HTTPS still see browser warnings that pages are not fully secure. Images, icons, stylesheets and form submissions continue to load over plain HTTP, and some product pictures show as broken boxes with a missing-file error. Owners with hundreds of product pages say they cannot edit each link by hand, and some do not know whether the extension rewrites external resources too. The result is an apparently secure site that still warns visitors and hurts trust, search ranking and checkout conversion.
AI-assisted: written with the help of AI from the reports.
Products affected
Forced SSL Everywhere OC 1.x - 3.x.
Related problems
Who has this problem
3 businesses found.
Unlock them at the top of this page — $57.
All sales are final — no refunds.
Each business's name, the address it published, and the page it was published on. Paid through Stripe; you get a private page to bookmark, with a CSV download.