Record the affected hostname, URL, operation, status code and precise time. Identify the installed web server and PHP runtime. Use authorized access and sanitize tokens, cookies, personal data and credentials before sharing excerpts.

1. For a website failure, use the available domain or raw/error log views and locate entries around the recorded request time. Reproduce the problem once with safe test data if necessary.
2. Inspect the application private log as well. A web server may report only an upstream failure while the application records the original exception.
3. For a panel problem, inspect Admin Logs > Error Logs. Webuzo documents its own error log at /var/webuzo/logs/error_log.log; this is not automatically the website PHP error log.
4. For authorized server diagnosis, locate the installed service logs. Webuzo Apache commonly uses /usr/local/apps/apache2/logs, while other managed servers and PHP versions have their own paths. Confirm the active configuration rather than using an old runtime example.
5. Classify the first relevant error: permission denial, missing file, invalid configuration, unavailable upstream, exhausted resource or application exception. Make one evidence-based correction.
6. Repeat the same safe request and compare new entries. Preserve a concise incident record before normal log rotation removes the evidence.

Start with the first error tied to the failed operation and timestamp. Later warnings can be consequences of that failure rather than independent problems.

Confirm the original failure is gone and that the corresponding successful operation reaches the expected application. Test an adjacent function and check for new errors after the change. A quiet log is not proof of health if logging itself is broken.

If no entry appears, confirm the request reaches this host and inspect proxy or DNS paths. Avoid exposing detailed errors on public pages. If a log grows rapidly, address the repeated cause and use proper rotation rather than deleting an actively written file blindly.

• Restarting only the affected Webuzo service
• Adjusting per-domain PHP settings in Webuzo
• Configuring log rotation for a custom Linux application
• Adding a domain and website in Webuzo

• Webuzo: Apps Log Path
• Webuzo: Error Logs