How to Troubleshoot a Joomla Website That Is Not Working
Define exactly what is failing
Start with the specific symptom: blank page, HTTP error, redirect loop, broken layout, database message, Administrator failure, or only one component that does not work. Test both the frontend and Administrator area when possible. A precise symptom prevents unrelated configuration changes from creating a second problem.
Check whether the failure is site-wide
Try a known public article, the Administrator login, and any unaffected subdomain or static file. If only one menu item or extension fails, focus there. If every PHP page fails, include PHP, web-server, database, filesystem, and hosting changes in the investigation.
Review the most recent change
Identify what changed immediately before the failure: Joomla or extension update, PHP version, template edit, plugin activation, migration, DNS change, certificate renewal, server rule, or restored backup. Do not assume the newest change is guilty, but use it to prioritize checks.
Expose useful errors temporarily
If Administrator still works, Joomla provides Error Reporting under Global Configuration → Server. Maximum reporting can reveal the PHP error behind a generic failure. For deeper diagnostics, Debug System can also be enabled for a controlled test. Do not leave detailed errors or debug output exposed on a public production site.
Check logs before guessing
Review Joomla logs, PHP error logs, web-server logs, and hosting control-panel events around the exact failure time. The first relevant fatal error, exception, denied request, or database error is usually more useful than secondary messages generated after the application has already failed.
Separate Joomla from the hosting layer
Confirm the supported PHP version and required PHP extensions, database availability, disk space, file permissions, TLS certificate, and web-server configuration. A Joomla page cannot recover from a full disk, unavailable database, invalid server rule, or PHP process failure.
Make one reversible correction at a time
Back up the site before invasive changes. Correct the first verified cause, clear only the relevant cache, and retest the original failing URL. Avoid mass-disabling extensions, deleting cache directories blindly, or replacing core files until evidence points to those actions.
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.