How to Troubleshoot a Joomla Site That Suddenly Stopped Working
Record exactly what changed and what fails
Before changing the site, record the first known failure time, affected URLs, HTTP status or visible message, and whether Administrator still loads. Check whether a Joomla or extension update, deployment, hosting change, DNS change, certificate renewal, PHP change, or configuration edit happened immediately beforehand. A precise timeline narrows the search much faster than clearing caches or disabling extensions at random.
Check the logs immediately after reproducing the failure
Reproduce one representative failure and inspect Joomla, PHP, PHP-FPM, web-server, hosting, security, and CDN logs for the same timestamp. Preserve the first relevant fatal error, exception, denied request, timeout, or resource message. If Joomla never logs the request, investigate the web server, proxy, firewall, DNS, or hosting layer before modifying Joomla content.
Separate frontend, Administrator, and infrastructure failures
Test the home page, a direct frontend article URL, and /administrator/ separately. If only one side fails, concentrate on extensions, templates, modules, plugins, authentication, or routing specific to that application. If both fail, verify DNS, TLS, PHP service health, database connectivity, disk space, server resources, and recent hosting changes before assuming Joomla core is damaged.
Review recent extensions and configuration changes
If logs point to an extension or the failure began immediately after an update or enable action, verify that extension's current Joomla and PHP compatibility. Use Administrator to disable only the confirmed noncritical suspect when possible. If Administrator is unavailable, use a documented recovery method and a database backup rather than disabling multiple extension rows blindly.
Verify the current Joomla 6 hosting requirements
For Joomla 6.x, current Joomla technical requirements list PHP 8.3 as the supported minimum and PHP 8.4 as recommended, along with required PHP modules such as json, simplexml, dom, zlib, gd, and a supported database driver. A host-side PHP or module change can therefore break a previously working site even when Joomla files were untouched.
Check resources and storage before restoring a backup
Confirm available disk space, database availability, PHP memory, process limits, and hosting account quotas. A full filesystem or exhausted resource pool can make Joomla fail suddenly and can also make restoration attempts incomplete. Preserve a current backup and logs before rolling back so the evidence needed to identify the actual cause is not lost.
Apply one evidence-based correction and verify broadly
Correct the confirmed extension, PHP, database, server, DNS, certificate, or configuration issue, then repeat the original request and test several frontend and Administrator workflows. Review the logs again for recurrence. Restore normal debugging and security settings after diagnosis and document the cause so a future sudden outage can be recognized quickly.
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.