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

Security

Mixed content warning: why an HTTPS page can still be insecure

Published August 2026 · 7 min read

An HTTPS page can still request images, scripts, stylesheets, frames, or other resources using plain HTTP. Browsers may block active mixed content or warn because part of the page would bypass the encrypted connection.

Use browser developer tools to identify the exact URL

The console and network panel can show which resource is loaded insecurely and which page requested it. Fixing the certificate will not rewrite an `http://` URL embedded in HTML or application data.

Check application and database URLs

CMS migrations commonly leave old absolute URLs inside content, theme settings, widgets, generated CSS, or serialized configuration. Use application-aware replacement tools rather than blind text substitution on a database.

Update third-party dependencies or remove them

If an external script, font, iframe, or image source does not support HTTPS, replace it or host an appropriate asset through a secure path. Do not weaken browser security to preserve an obsolete dependency.

Verify redirects do not hide the problem

A resource requested over HTTP may redirect to HTTPS, but the initial insecure request can still be undesirable and security policies may block it. Update source URLs to the canonical secure address directly.

Next step

Mixed content occurs when an HTTPS page requests resources over HTTP. Find hard-coded URLs, database content, stylesheets, scripts, images, proxies, and third-party dependencies.

Read TLS and security guides

Keep reading

Related guides.

Content Security Policy rollout: build CSP from the resources a site really uses

Inventory scripts, styles, frames and connections, start with reporting, reduce unsafe allowances and enforce CSP only after normal user paths still work.

Read the guide

HSTS rollout planning: enable strict HTTPS without locking in a mistake

Stabilize HTTPS first, choose max-age carefully, cover subdomains deliberately and understand preload consequences before making HSTS hard to reverse.

Read the guide

HTTPS redirect mistakes: loops, chains and host changes that hurt a site

Find conflicting HTTP-to-HTTPS and hostname redirects across proxies, servers and applications, then reduce the path to one intentional canonical destination.

Read the guide

More security 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