How to Troubleshoot a Joomla Website That Is Not Working

Write down what “not working” means: blank page, HTTP 500, 403, redirect loop, database error, broken layout, missing assets, Administrator failure, or one extension that fails.

Define the failure precisely

Write down what “not working” means: blank page, HTTP 500, 403, redirect loop, database error, broken layout, missing assets, Administrator failure, or one extension that fails. Test a known frontend article and the Administrator login separately. A precise symptom keeps troubleshooting focused and prevents unrelated changes from creating a second problem.

Check scope and the most recent change

Determine whether the failure affects every PHP page, only one menu item, only logged-in users, or only one extension. Then identify recent changes such as Joomla or extension updates, PHP changes, template edits, DNS changes, certificate renewals, migrations, restored backups, or web-server rules. Use those changes to prioritize checks, not as proof of cause.

Capture the real error before guessing

If Administrator works, temporarily raise Error Reporting under Global Configuration → Server and reproduce the failure. For deeper controlled diagnostics, enable Debug System only when needed. Also inspect Joomla, PHP, web-server, and hosting logs at the exact failure time. Capture the first relevant fatal error or exception and then restore production-safe reporting.

Verify the hosting layer

Confirm that PHP is running, the database is reachable, disk space and inode limits are healthy, required PHP extensions are present, file ownership is correct, and the TLS certificate and web-server configuration are valid. Joomla cannot repair a full disk, stopped database service, invalid rewrite rule, or broken PHP handler.

Isolate extensions and templates safely

If evidence points to an extension or template, reproduce the issue on staging and disable or switch one noncritical item at a time. Do not mass-disable production plugins, especially authentication or security plugins. Keep a rollback path and retest the exact failing URL after every change.

Repair the first verified cause

Apply the smallest correction supported by the error and logs: fix a configuration value, restore a damaged file from a trusted package or backup, correct a server rule, update an incompatible extension, or repair the database using Joomla’s supported tools. Avoid random core-file replacement or broad permission changes.

Verify recovery and prevent recurrence

Retest frontend and Administrator access, login, forms, key extensions, and the original failing URL. Review logs for new errors and restore normal error-reporting settings. Document the root cause and correction so the same failure can be recognized quickly after future updates or hosting changes.


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.

Open a Support Ticket