Skip to content

Knowledgebase & Docs

Search guides, configuration tutorials, API references, and troubleshooting solutions.

Quick Topics: Getting Started Email Configuration Domains & DNS KBilling — Start Here KBilling — Administration

Fix an HTTP 500 or blank page

Category: Fix Common Errors 1 Views 0 Helpful Votes

Find PHP bootstrap, syntax, database and deployment failures without exposing production errors to visitors.

Start with the change boundary

Identify the exact file, package or setting changed immediately before the failure. If only one route is broken, inspect that route’s controller, template and module before changing global server settings.

Collect evidence safely

  1. Check the hosting error log, PHP-FPM log and web-server log for the request timestamp.
  2. Confirm the deployed files are complete and in the correct document root.
  3. Validate the active PHP version and required extensions.
  4. Check file ownership and read permissions.
  5. Restart PHP-FPM or clear OPcache only after confirming the corrected file is deployed.

Common causes

  • A partial ZIP extraction or nested application directory.
  • A PHP syntax feature unsupported by the active runtime.
  • Missing configuration.php, invalid database credentials or unavailable database.
  • Schema not upgraded for the deployed code.
  • A module throwing during page rendering.
Do not enable public error displayUse server-side logging. Production stack traces can expose paths, SQL, credentials and customer information.
Was this article helpful to you?
Back to Fix Common Errors Contact Support