How do I redirect HTTP to HTTPS and fix mixed content? Print

In short: Install and verify the SSL certificate first, then configure one permanent redirect from HTTP to the preferred HTTPS hostname. Finally, correct any page resources that still use insecure HTTP URLs.

Before redirecting

• Confirm HTTPS works for the bare domain and any www hostname you intend to use.
• Choose one canonical hostname.
• Back up the current .htaccess file and application configuration.
• Check whether WordPress or another application already controls redirects.

Create one redirect

Use the application setting or SiteWorx Hosting Features > Htaccess tools where possible. Redirect every HTTP path to the equivalent path on the chosen HTTPS hostname, and use a permanent redirect only after testing.

Fix mixed content

A page is mixed content when its HTML loads over HTTPS but an image, stylesheet, script, font or frame still uses HTTP. Use the browser console to identify the URL, then update the application content, theme or asset configuration to use HTTPS.

WordPress checks

• Set both WordPress Address and Site Address to the intended HTTPS URL.
• Replace old HTTP URLs in database content using a serialisation-aware tool.
• Clear application, proxy and browser caches.
• Confirm scheduled jobs and webhooks use the new address.

Verify the result

• HTTP redirects once to the intended HTTPS URL.
• Paths and query strings are preserved.
• No certificate or mixed-content warnings appear.
• Forms, login, payments and callbacks still work.

Further guidance

See the InterWorx documentation for SSL certificates and SiteWorx .htaccess management.