Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am configuring elysia_cron on a Rackspace Managed Cloud Server. We have a loadbalancer in front of two webservers. Am I supposed to use all three (3) IP addresses (Load Balancer, Web01, Web02) in the "Allowed Hosts" field? or just use the IP address of the Load Balancer?

share|improve this question
up vote 2 down vote accepted

I think you'll find you only need to allow your web nodes, not the balancer.

You may also want to read up on how Elysia handles cron access; allowed hosts is intended to avoid external cron calling. Is this something you are want to exclude? If you really need to secure your servers, Elysia also allows you to set a cron_key to restrict access.

However, it sounds like you're just looking for a recommended default setting.

Edit: On Deer Hunter's suggestion, I could elaborate that the standard configuration is for a cron job, running on the machine on which Drupal is installed, to 'hit' Drupal cron by issuing a get request for cron.php. Thus on an HA deployment, this request originates from a web node. Unless you foresee needing cron to be triggered across the public internet, you only need your web nodes white-listed. HTH.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.