Hello,
Would you mind opening a support ticket about this? cPanel Customer Portal
My first guess is that the affected user is using jailshell (or no shell access) or is under CloudLinux' CageFS, and don't have access to that file. It could also be that there is some difference in the environment; the environment of cron jobs is substantially different from that of the command line. It could also be something totally different.
As a workaround, you might have your user execute the cron job via web request rather than from the command line, with wget -O https://domain.tld/path/to/cron.php. For security, you should configure .htaccess for the directory containing the php cron script so that it can't be accessed by IP addresses other than 127.0.0.1 or ::1.
David Nielson
Would you mind opening a support ticket about this? cPanel Customer Portal
My first guess is that the affected user is using jailshell (or no shell access) or is under CloudLinux' CageFS, and don't have access to that file. It could also be that there is some difference in the environment; the environment of cron jobs is substantially different from that of the command line. It could also be something totally different.
As a workaround, you might have your user execute the cron job via web request rather than from the command line, with wget -O https://domain.tld/path/to/cron.php. For security, you should configure .htaccess for the directory containing the php cron script so that it can't be accessed by IP addresses other than 127.0.0.1 or ::1.
David Nielson
Okay, I'll open up a ticket. One account is a jailed shell, the others have their shell disabled. We are not using cloudlinux. These jobs worked before the 54 update.
Hi,
As an update, we've opened case CPANEL-3680 and we're working on getting a fix in ASAP. Thanks!
As an update, we've opened case CPANEL-3680 and we're working on getting a fix in ASAP. Thanks!
This is a huge issue and has caused a big issue with billing and a lot of other problems on my server with WHMCS and my clients are having issues as well.
Morning,
This issue was fixed in v54, and the fix is in v56 and v58. Are you still getting errors?
This issue was fixed in v54, and the fix is in v56 and v58. Are you still getting errors?
I can confirm that this issue was resolved way back just after I opened the thread!
