How to Force HTTPS in Joomla
Joomla can force visitors and administrators onto HTTPS, but the server must already have a valid TLS certificate and be able to serve the site securely. Configure HTTPS in the right order so you do not create redirect loops, mixed content, or an Administrator lockout.
Verify HTTPS works before forcing it
Open the site directly with https:// and confirm the certificate is valid for the canonical hostname. Test the frontend, Administrator login, forms, and important extension routes. Fix certificate, hostname, proxy, or server problems before enabling redirects.
Enable Force HTTPS in Global Configuration
In Joomla Administrator, open System → Setup → Global Configuration, choose the Server tab, and locate Force HTTPS. Select Entire Site when both frontend and Administrator traffic should use HTTPS, then save. Use Administrator Only only when that split is intentional.
Avoid competing redirect layers
Hosting panels, Apache or Nginx rules, CDNs, reverse proxies, and load balancers can also redirect HTTP to HTTPS. Choose a clear redirect design and make sure every layer agrees about the original request scheme. Conflicting rules can create loops or repeated redirects.
Correct mixed-content and hard-coded HTTP URLs
Use browser developer tools to find scripts, stylesheets, images, fonts, iframes, form actions, or API requests still using http://. Correct the source in content, templates, modules, plugins, extension settings, or custom code. Avoid indiscriminate database-wide replacement.
Test redirects and secure sessions
Request several http:// URLs, including deep routes with query strings, and confirm they reach the matching https:// URL without losing the path or looping. Test frontend and Administrator login/logout and verify sessions remain stable behind any proxy or CDN.
Verify the public site from a clean session
Use a private browser window and test representative guest, authenticated, and Administrator workflows. Confirm the certificate, redirect chain, final HTTPS URL, secure resources, and canonical hostname are consistent. Purge relevant caches only after the source configuration is correct.
Need More Help with Joomla?
Still having trouble? Open a support ticket with QuantaCade Support and we'll be happy to help where we can.
Support priority is given to QuantaCade products, services, and customers. However, we're also happy to assist fellow Joomla users with general Joomla questions and troubleshooting when possible.
QuantaCade is an independent Joomla extension developer and is not official Joomla support. Some issues involving third-party extensions, hosting environments, server configurations, or other systems outside our development control may be beyond what we're able to resolve.