πŸ“Š
Plesk

Debugging Cronjob Errors in Plesk

πŸ“… 8 October 2026 ✏️ 8 October 2026 ⏱ 5 min leestijd

Resolve cronjob errors in Plesk: reading log files, recognizing common mistakes, and debugging step by step on your server.

If a cronjob in Plesk isn’t running, you often won’t see a direct error message on your screen – the script simply fails in the background. The answer usually lies in the log files: there you’ll find exactly what went wrong, whether it’s an incorrect PHP path, a missing environment variable, or a permission issue. In this article, you’ll systematically walk through the debugging process, from reading logs to solving the most common causes.

How cronjobs work in Plesk

A cronjob is a scheduled task that runs automatically at fixed times, for example to synchronize a database, send emails, or call a backup script. In Plesk you configure these tasks via Websites & Domains β†’ Scheduled tasks (cronjobs), where you link a command or script to a time schedule.

On servers with LiteSpeed and NVMe storage, the cron service runs independently of your web server, which means a slow website isn’t automatically the cause of a failed cronjob – and vice versa. The difference between a working and a failing task is often small: a missing absolute path, an incorrect PHP version, or a variable that exists in an interactive shell but not in the cron environment.

CronjobLog fileSolution

Checking and interpreting log files

The first step in debugging a cronjob is always to check the log file. In Plesk you can find this via Websites & Domains β†’ Scheduled tasks, where you can view the execution history per task, or via Logs at the domain level.

1

Open Plesk and go to your domain

Log in to Plesk and navigate to the relevant domain under Websites & Domains.

2

View the scheduled tasks

Open the cronjob and click on the execution history to see the latest runs and their status.

3

Find the error message

Pay attention to timestamps that match the scheduled time of the task and read the full error line.

4

Trace the cause

An error message like ‘command not found’ often indicates an incorrect path, while ‘permission denied’ points to permission issues.

πŸ’‘ Tip: Always have the cronjob write its output to its own log file, for example by adding >> /path/to/log.txt 2>&1 to the command. This way you’ll always have a complete history, even if Plesk itself shows limited logging.

Solving common problems

Most cronjob errors come down to a handful of causes:

Incorrect PHP path: many tasks fail because the absolute path to PHP is missing or doesn’t match the desired PHP version. Check via SSH with which php which path is correct, and always refer to the full path in the cronjob instead of just php.

Missing environment variables: cron runs in a minimal shell without the variables you’re used to in an interactive session. Set required variables such as $PATH or $HOME explicitly in the script itself.

Permission issues: the script must be executable (chmod +x script.sh) and the user under which the cronjob runs must have access to all files and folders that the script accesses.

Timeouts on long-running tasks: large imports or backups can get stuck if the execution time is too short. Split heavy tasks into smaller steps or schedule them outside peak times.

Relative paths in scripts: a script that works locally but fails in cron often uses relative paths that depend on the working directory. Always use absolute paths to files and folders.

Testing cronjobs and preventing errors

Test a new cronjob manually via SSH first by executing exactly the command as configured in Plesk. This way you’ll see error messages immediately instead of waiting for the next scheduled run.

Also take dependencies into account: if a cronjob sends emails, check whether your email configuration is set up correctly, for example via business email with the correct SPF and DKIM records. If the task runs on a new domain, also check whether the domain name and DNS have been correctly propagated before expecting scripts to be externally reachable.

If you’re still stuck despite these steps, consult the knowledge base for more Plesk explanations or contact support.

Frequently Asked Questions

Why does my cronjob show no output at all?

Often because the output isn’t being captured. Add >> /path/log.txt 2>&1 to the command so both normal output and error messages are written to the file.

My script works via SSH but not via cron, how is that possible?

This is almost always due to missing environment variables or relative paths. Use absolute paths and set required variables explicitly in the script.

How do I know which PHP version my cronjob uses?

Check this via SSH with which php or php -v, and make sure the path in the cronjob exactly matches the desired version.

Can I run multiple cronjobs at the same time?

Technically yes, but with heavy tasks you may cause server load. Spread tasks throughout the day, especially on shared web hosting.

What do I do if none of this helps?

Collect the full error message and the exact command and contact support, who can look into the server logs.

Conclusion

Cronjob errors in Plesk can almost always be traced back to a log line: so always start with the log files, check paths, permissions, and environment variables, and test commands manually via SSH first. With a structured approach, you’ll solve most errors within minutes.

View web hosting β†’

Was dit artikel nuttig?