WHM Administration: Build a Repeatable Account Troubleshooting Checklist

When a cPanel account reports a website failure, gather evidence before changing global server settings. Start with the domain's document root, account status, DNS resolution, and the exact HTTP response.

Check the account's resource usage, PHP version, PHP-FPM pool, error logs, and disk or inode limits. A 500 error may come from application code, permissions, exhausted resources, or a missing PHP extension. Identify which layer reports the error before applying a fix.

Use the account's configured PHP binary when running Composer or Artisan. Confirm that generated cache files belong to the account user and that only required directories are writable. If the issue affects one account, avoid global changes that could interrupt other tenants.

After correction, verify the public URL, review recent logs, and document the root cause. For recurring issues, create a small checklist that captures the commands and expected evidence. Consistent diagnostics reduce recovery time and prevent risky guesswork under pressure.