Due to the differences between hosts, we get more questions about cron (scheduled) tasks than almost anything else.

Your webhost is your best ally for this as they should fully understand the details need to successfully set up the cron (scheduled) task. If you get someone on frontline support who has no clue what you are talking about, ask to be referred to a technical level of support. Any technical support person with even a mid-range knowledge of server setups will fully understand how to do this.

The arpReach user guide contains detailed installation instructions (including the cron task) and is available for download from the hub:


In summary, the cron (scheduled) task must be set up as follows:

php /path/to/your/public_html/arpreach/a.php cli/auto

...where php (php-cli on a CPanel server) is a PHP5 (must be PHP version 5) command line interpreter and the path is the exact absolute path to the a.php script that is part of arpReach.

Other variation that sometimes work (but ask your webhost!) are:

  • /usr/local/bin/php
  • php5
  • php52
  • php53
  • /usr/local/bin/php5
  • /usr/local/bin/php52
  • /usr/local/bin/php53
  • /opt/cpanel/ea-php55/root/usr/bin/php

Note that there IS a space after a.php and before cli/auto. This is correct no matter what your host support desk might say.

It is NEVER correct to use "wget" or "lynx" or with any kind of "http" URL in the cron setup as this means it's going to pass through your webserver as a "browser" task and simply get terminated when it runs for more than a few minutes.

If you need professional assistance then we highly recommend the following installation service: