Website Logs in Plesk

Logs help you understand why a site shows an error or does not behave as expected. Go to Websites & Domains → your domain → Dashboard tab → Dev Tools group → Logs.

The Logs page
The Logs page

What is on the page

  • The list at the top right selects the log: site access or errors.
  • The From filter and the Message field search by time and by entry text.
  • Start real-time updates shows new entries as they arrive. Turn it on, open your site in another tab, and reproduce the error.
  • Refresh reloads the list.
  • Manage Log Files lists the log files so you can download or delete them.
  • Log Rotation sets how often logs are split into parts and how many old parts to keep.

Failed Request Tracing

If the logs only show an error code and the cause is unclear, turn on IIS request tracing: in the Dev Tools group, open Failed Request Tracing and click Start Tracing. Reproduce the error on the site, and reports for failed requests appear in the list. You can download them with Download ZIP.

Failed Request Tracing
Failed Request Tracing

Tracing is resource-intensive and slows the site down. Turn it off as soon as you have the reports you need, and delete them with Remove.

Common mistakes

  • Logs are not rotated and take up a lot of space over time. Check the Log Rotation settings.
  • Looking for an ASP.NET Core error in the general log. For detailed application messages, see ASP.NET Core in Plesk.
Questions and answers
Logs fill up as people visit the site. Open the site, refresh the Logs page, and make sure the right log is selected in the list.
Find the time of the error in the error log and turn on Failed Request Tracing. Common causes are in common site errors.