Collect the affected hostname, URL, time with timezone, response code and a brief description of the action. Confirm that you are looking at the correct domain rather than the parent site or another subscription. Preserve incident evidence before rotating or deleting logs.

1. Open Websites & Domains > Logs for the affected domain.
2. Select the required log sources and narrow the time or text filter. Start with access and error entries around the same request.
3. Use real-time updates for one controlled reproduction if that operation is safe. Stop repeated tests that create orders, send messages or alter customer records.
4. Open Manage Log Files when you need the original file or a download for deeper analysis. Review application-specific logs separately when the failure occurs inside the application.
5. Use the evidence to distinguish a missing file, permission denial, rejected request, backend timeout or application exception. Record the first causal error rather than only the final status.

After a targeted change, repeat the same harmless request and compare the new entries. Confirm the response is correct and no new warnings or failures appear. Check one nearby workflow as well.

If the request is absent, it may be reaching another server, a CDN cache or a different virtual host. Compare DNS and proxy routing before assuming logging is broken. If the browser truncates a large entry, inspect the protected source file. Do not publish full logs containing session tokens, email addresses or confidential query parameters.

• Finding PHP errors for a Plesk website
• Configuring website log rotation in Plesk
• Knowing when Plesk DNS changes control public records
• Diagnosing a ModSecurity false positive in Plesk

• Plesk: Log Files