Cron error after update git 14082026 #5919
Replies: 1 comment 3 replies
|
e107 Schedule Tasks (crons) needs an ergonomic revamp. After evaluating the implementation, I now intend to walk back the restrictions introduced by e904dd9 for e107 v2.3.3. It will once again be possible to run crons over HTTP with a token, with the main benefit being that the PHP over HTTP is the same version of PHP that the site runs. |
|
@Alex-e107nl the two pull requests for what Deltik described above are up: #5943 for master and #5944 for Once merged, Admin > Schedule Tasks gets a Setup tab that prints that line for your server (and the
And the Manage tab will say when calls are being refused instead of leaving it to the Apache error log; a wrong or missing token gets a plain
|
|
Looks very good, i will merge again and test it. |
|
@Alex-e107nl both merged on 16 August, #5943 into Nothing to change on your side: the |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
PHP 8.3, updated e107 to github 15-08-2026
[Sat Aug 15 04:57:01.594222 2026] [proxy_fcgi:error] [pid 1042198:tid 1042389] [remote *************:33316] AH01071: Got error 'PHP message: e107: cron.php refused a request that arrived over HTTP (PHP_SAPI: fpm-fcgi); cron.php is command line only'
Existing cron in DA, nothing changed, was working, error now...
/usr/bin/curl https://www.**********/cron.php token=6a06c3a9dbde140a76499644e4fa680c4066fbc5 >/dev/null 2>&1
This is what e107 gives me with a new token generated:
/home//domains//private_html/cron.php token=ec723e3a3fd73ebe78d350c967300e1********** >/dev/null 2>&1
Should be used like this in Direct Admin:
/usr/bin/php /home//domains//private_html/cron.php token=ec723e3a3fd73ebe78d350c967300e1********** > /dev/null 2>&1
Error gone now, should be documented!
Did not see this for a long time, so maybe it was not working but now it does again!
All reactions