Answers.Body: <p>I was able to add the following line to my System.php file and run the cron from my Chrome browser one time to see what was actually being passed. </p>
  
  <p>At Line 570 I went from:</p>
  
  <pre><code>    if ($key !== $siteKey) {
    return self::authenticateAbort(
      "ERROR: Invalid key value sent. " . $docAdd . "\n",
      $abort
    );   
  }
  </code></pre>
  
  <p>To:</p>
  
  <pre><code>`return self::authenticateAbort(
          "ERROR: Invalid key value sent. " . $docAdd . $key . $siteKey ."\n",
          $abort
        );
      }`  
  </code></pre>
  
  <p>So the cron is running, but I am getting header errors now. Hey at least this one is solved. </p>
  
  <p>Found most of the answer here: <a href="https://civicrm.stackexchange.com/questions/16627/cron-invalid-key-value-sent/16634#16634">Cron - Invalid key value sent</a></p>
  
  <p>Though the log wasn't generating the lines I needed, so I just ran with it. My solution isn't the most secure, but it got the job done after a month of manually running jobs. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-10T17:57:44.547Z
Answers.LastActivityDate: 2017-05-10T17:57:44.547Z
Answers.UserDisplayName: Tiffany Carra
Answers.Body: <p>Looks like your user name for this is 'cronjobs'. try creating a new user without the word 'cron' in it. I had a similar issue with a new site recently and removing 'cron' from the user name did the trick.</p>
  
  <p>Hope this helps.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-28T17:49:22.143Z
Answers.Text: Let me try that
Answers.UserDisplayName: Tiffany Carra
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-28T17:53:20.513Z
Answers.Text: same thing with me admin login that I typically use to login.
Answers.UserDisplayName: Tiffany Carra
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-28T14:03:56.623Z
Answers.LastActivityDate: 2017-03-28T14:03:56.623Z
Answers.UserDisplayName: KilakwaBT
Body: <p>Ok I did search and I do recall fussing with this a bunch when setting up cron jobs, but here is the situation. </p>
  
  <p>I accidentally deleted my civicrm-settings.php file the other day. Really it was no big deal, restored within 5 minutes from a backup only a few hours old. HOWEVER, since then cron has not been running. </p>
  
  <p>Trying to pull it via: 
  wget -O - -q -t 1 '<a href="http://www.SITE.com/wp-content/plugins/civicrm/civicrm/bin/cron.php?name=cronjobs&amp;pass=#####&amp;key=####" rel="nofollow noreferrer">http://www.SITE.com/wp-content/plugins/civicrm/civicrm/bin/cron.php?name=cronjobs&amp;pass=#####&amp;key=####</a>'   </p>
  
  <p>I have been getting: </p>
  
  <p>ERROR: Invalid key value sent. More info at:<a href="http://wiki.civicrm.org/confluence/display/CRMDOC/Managing+Scheduled+Jobs" rel="nofollow noreferrer">http://wiki.civicrm.org/confluence/display/CRMDOC/Managing+Scheduled+Jobs</a></p>
  
  <ul>
  <li>Absolutely nothing has changed</li>
  <li>Verified Site Key</li>
  <li>Verified administrator un/pw</li>
  </ul>
  
  <p>Tried running it with cli.php and it is still not running (despite setting permissions on that file)</p>
  
  <p>Any incite?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-04-05T05:47:48.637Z
Comments.Text: Still having issues with this. Having to run scheduled jobs manually daily
Comments.UserDisplayName: Tiffany Carra
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-05-10T03:16:59.483Z
Comments.Text: STILL AN ISSUE. Upgraded to 4.7.19
Comments.UserDisplayName: Tiffany Carra
Tags: <wordpress><cron-job><tutorials>
Title: Wordpress Cron Issues
ThreadText: # Wordpress Cron Issues
  
  (Asked by: username_0 on 2017-03-23)
  
  Ok I did search and I do recall fussing with this a bunch when setting up cron jobs, but here is the situation.
  
  I accidentally deleted my civicrm-settings.php file the other day. Really it was no big deal, restored within 5 minutes from a backup only a few hours old. HOWEVER, since then cron has not been running.
  
  Trying to pull it via:
  wget -O - -q -t 1 '<http://www.SITE.com/wp-content/plugins/civicrm/civicrm/bin/cron.php?name=cronjobs&pass=#####&key=####>'
  
  I have been getting:
  
  ERROR: Invalid key value sent. More info at:<http://wiki.civicrm.org/confluence/display/CRMDOC/Managing+Scheduled+Jobs>
  
  * Absolutely nothing has changed
  * Verified Site Key
  * Verified administrator un/pw
  
  Tried running it with cli.php and it is still not running (despite setting permissions on that file)
  
  Any incite?
  
  **Tags:** wordpress, cron-job, tutorials
  
  > **Comments:**
  > **username_0**: Still having issues with this. Having to run scheduled jobs manually daily  
  > **username_0**: STILL AN ISSUE. Upgraded to 4.7.19  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2017-05-10. Score: 0 | Accepted answer
  
  I was able to add the following line to my System.php file and run the cron from my Chrome browser one time to see what was actually being passed.
  
  At Line 570 I went from:
  
  ```
      if ($key !== $siteKey) {
    return self::authenticateAbort(
      "ERROR: Invalid key value sent. " . $docAdd . "\n",
      $abort
    );   
  }
  
  ```
  
  To:
  
  ```
  `return self::authenticateAbort(
          "ERROR: Invalid key value sent. " . $docAdd . $key . $siteKey ."\n",
          $abort
        );
      }`  
  
  ```
  
  So the cron is running, but I am getting header errors now. Hey at least this one is solved.
  
  Found most of the answer here: [Cron - Invalid key value sent](https://civicrm.stackexchange.com/questions/16627/cron-invalid-key-value-sent/16634#16634)
  
  Though the log wasn't generating the lines I needed, so I just ran with it. My solution isn't the most secure, but it got the job done after a month of manually running jobs.
  
  
  ---
  
  ### Answer by username_1 on 2017-03-28. Score: 0
  
  Looks like your user name for this is 'cronjobs'. try creating a new user without the word 'cron' in it. I had a similar issue with a new site recently and removing 'cron' from the user name did the trick.
  
  Hope this helps.
  
  > **Comments:**
  > **username_0**: Let me try that  
  > **username_0**: same thing with me admin login that I typically use to login.  
  
  ---
  
  