How to Troubleshoot “An Error Has Occurred” in Joomla

Joomla's “An Error Has Occurred” screen is a presentation of an underlying exception or failure, not a diagnosis by itself. Capture the exact request and timestamp, reveal or locate the real error safely, identify the code or service that owns it, and change only the condition supported by that evidence.

Capture the failure before changing the site

  1. Record the complete visible message and any error code.
  2. Record the exact URL, action, timestamp, and whether the user was signed in.
  3. Determine whether the problem affects the frontend, Administrator, one component, one account, or the entire site.
  4. Test a nearby known-good route to narrow the scope.

Do not start by reinstalling Joomla, deleting caches indiscriminately, or disabling several extensions. Those actions can remove evidence without identifying the cause.

Use Joomla error reporting carefully

If Joomla can still start, temporarily increasing Error Reporting in Global Configuration can reveal a PHP warning, exception, file path, or stack information. Use detailed output only during controlled troubleshooting—preferably on staging—because it can expose internal paths and implementation details.

Restore the normal production error-reporting setting after collecting the evidence.

Read Joomla, PHP, and server logs

Match log entries to the recorded timestamp and request. Check Joomla logs, PHP error logs, web-server logs, database errors, and extension-specific logs where applicable. A failure that occurs before Joomla starts may exist only in the PHP or server log.

Focus on the first relevant fatal error or exception rather than unrelated notices generated by other requests.

Identify what owns the failing code

A stack trace, class name, component path, plugin name, template path, database table, or API endpoint can show whether the problem belongs to Joomla core, a third-party extension, custom code, hosting, or an external service.

  • For Joomla core, confirm the installed Joomla version and update state.
  • For an extension, check its version, compatibility, and developer-supported recovery path.
  • For custom code, reproduce the problem on staging before editing production.
  • For server or database failures, use the hosting or database evidence rather than modifying Joomla files.

Correlate the error with recent changes

Review core and extension updates, PHP changes, configuration edits, template work, deployments, database changes, and hosting changes made immediately before the failure. Chronology is useful, but confirm the relationship by reproducing the issue or safely reversing the specific suspect on staging.

Avoid editing Joomla core or vendor files as a quick fix. Updates can overwrite those edits and the modification can conceal the real defect.

Verify the correction and restore production-safe settings

  1. Make the smallest correction supported by the evidence.
  2. Repeat the original action.
  3. Test related frontend and Administrator workflows.
  4. Review the logs for new errors.
  5. Turn off temporary debug output and restore normal error reporting.
  6. Document the root cause and correction.

If the useful error remains outside Joomla—for example a PHP-FPM, web-server, database, or hosting failure—escalate with the exact timestamp and log evidence rather than continuing speculative Joomla 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