Cron job not running

[rickenbacker]

I would have replied to another thread (in bugs) regarding this but it's been closed.

 

I have just determined that my daily cron was not running (after upgrading to 5.2.13) because my whmcs admin directory is password protected, needless to say after testing, I have just re-enabled password protection and will run the cron manually until I can do otherwise. Is there anyway around this or is a fix required?

 

 

[h=2]Password Protect the Admin Directory[/h] Add a second layer of protection to the admin directory by setting up .htaccess password protection. Most users can do this via the Password Protect Directories option in cPanel. Remember to keep your .htaccess username/password distinct and unique. You can use the Random Password Generation feature in cPanel to help.

 

[imaticon]

Hi,

 

Password protection does not matter if you have setup the cron job using php cli (php -q /bla/bla/cron.php).

 

Do you see in your whmcs ActivityLog that the cron job has started?

Something like this? => dd/mm/yyyy hh:mm Cron Job: Starting

 

Regards,

Marco

[rickenbacker]

Hi, totally understand password protection should not affect the cron running, but in this case it just does! Only when I disable password protection does it run the cron on schedule as normal, otherwsie nothing, not even and entry in the activity log.

 

I should mention my crons have been running fine for years until 5.2.13. I've done a full file update to 5.2.14 but issue remains the same.

 

Yes cron setup using php -q /xxx/xxx/xxx/xxx/xxx/cron.php

 

Apache 2.4.6

PHP 5.4.20

Edited December 9, 2013 by rickenbacker

[neilw]

Was this ever solved? I have the same issue. Can run it manually/directly, but cron job does not execute the file. Have the admin dir password protected. Hosting company verifies that the cron job is actually running, but nothing in the WHMCS logs, no actions and no email.

[rickenbacker]

I also have admin directory password protected. I ended up backing up the database, wiping all files and doing a a complete clean install from scratch, cron started running as normal then.