πŸ“Š
Plesk

Viewing Error Logs in Plesk: Explanation and Step-by-Step Guide

πŸ“… 7 October 2026 ✏️ 7 October 2026 ⏱ 4 min leestijd

Learn where to find error logs in Plesk, what the different log types mean, and how to analyze error messages to quickly resolve issues.

Error logs in Plesk show you exactly what’s going wrong on your website: from server errors to faulty PHP code. You’ll find them under your domain in Log Files, where Plesk neatly separates logs per domain into error logs, access logs, and (if applicable) PHP error logs. By reviewing these logs regularly, you can resolve issues before visitors are affected.

Where to find error logs in Plesk

Log in to your Plesk panel and click on your domain name. Go to Log Files (sometimes called Logs, depending on your Plesk version and theme). Here you’ll find all the log files for your website in one place, including your web server’s error log and any PHP error logs. You can view the contents directly in your browser, download them as a file, or follow them live while you’re debugging.

Plesk PanelLog Fileserror_logPHP error_logaccess_log

Different log types explained

Plesk shows multiple log types by default, each with its own function:

  • Error logs show errors from your web server (Apache, Nginx, or LiteSpeed), such as configuration errors and critical server errors.
  • Access logs record every request to your website: which pages were visited, from which IP address, and with which browser.
  • PHP error logs contain errors in your PHP code, such as undefined variables, syntax errors, or deprecated functions. Essential if you’re running a CMS or custom script.
  • SSL/TLS-related messages may appear in the error log in case of certificate issues or handshake failures.
πŸ’‘ Tip: Check your logs even when you have no complaints. This way, you’ll catch small errors before they grow into an outage that affects visitors.

Recognizing and analyzing error codes

A line in the error log usually contains a timestamp, an error code, and a brief description. The most common error codes are:

  • 500 Internal Server Error β€” usually an error in your PHP code or server configuration.
  • 403 Forbidden β€” access denied, often due to incorrect file permissions.
  • 404 Not Found β€” the requested file no longer exists.
  • 502 Bad Gateway β€” a communication problem between the web server and the PHP processor.

Look for patterns: if the same error occurs repeatedly, it often points to a structural issue rather than a one-time glitch. Also pay attention to the timing: if a spike in errors coincides with an update or plugin installation, that’s likely the cause.

Step-by-step plan for debugging with logs

1

Open the Plesk panel

Log in and select the relevant domain from the list.

2

Navigate to Log Files

Click on ‘Log Files’ under your domain’s settings.

3

Choose the right log file

Select error_log for server errors or PHP error_log for code errors.

4

Analyze the messages

Review the most recent lines, paying attention to error codes, timestamps, and recurring patterns.

5

Take action

Adjust your code or permissions, or contact your hosting provider if it concerns a server configuration issue.

If your website runs on multiple domains with associated mailboxes, also check whether error messages are related to your business email or DNS settings for your domain names. Considering switching to a provider with better insight and faster support? Check out switching to Tandata.

Frequently Asked Questions

How far back do error logs in Plesk go?

This depends on server settings and available disk space. If you want to keep old logs, download them in time via the Plesk panel.

Can I get automatically alerted to errors?

Can I get automatically alerted to errors?

Yes, with monitoring tools or Plesk extensions you can set up email alerts so you’re immediately notified of critical errors.

What does ‘permission denied’ mean in a log file?

This usually indicates incorrect file permissions. Check that folders are set to 755 and files to 644.

Am I allowed to delete old log files?

Yes, this can be done via Plesk. However, make a backup first if you think you might need the data later.

Where can I find more help reading logs?

Check our knowledge base for more explanations about Plesk features, or contact our support team.

Conclusion

Error logs in Plesk give you immediate insight into what’s going wrong on your website. By regularly checking the error log, PHP error log, and access log, you’ll catch problems early and resolve them effectively. Combine this with stable web hosting and you’ll stay in control of your site’s performance and reliability.

View web hosting β†’

Was dit artikel nuttig?