Answers.Body: <p>Since you're using a <code>wget</code>-based cron, there should be a corresponding entry in the web server log for each cron run.  Look to see the Apache value - does it return <code>404</code> or <code>500</code> or maybe something else?  <code>404</code> would indicate a wrong URL; <code>403</code> would indicate it's blocked, perhaps because of the user agent (iThemes Security for WordPress does this in its default configuration).  A <code>200</code> or <code>500</code> would mean to check the CiviCRM log in ConfigAndLog.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-12-20T05:55:23.550Z
Answers.LastActivityDate: 2017-12-20T05:55:23.550Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.Body: <p>I had an issue like this once.  The cron was being run by logging in with a username and password and the password for that user had changed so the cron was not able to access properly.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-06-23T03:25:14.320Z
Answers.Text: Nope, the password is correct. I'm the only one who has access to the users. I even went and copied the password from the cron and made sure it was the same for the user. It was. Username is correct as well. Has full CiviCRM priviledges.
Answers.UserDisplayName: Jenni Simonis
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-06-22T22:39:28.910Z
Answers.LastActivityDate: 2017-06-22T22:39:28.910Z
Answers.UserDisplayName: MBrown
Body: <p>We use CPanel to run crons on our sites. The cron had been working fine and then stopped some months back. I've tried every example I can find, but it still is not running properly.</p>
  
  <p>I've attached a screenshot of what the cron looks like in CPanel as well as the cron in text (redacted to remove personal info). The username, password, and key are all letters/numbers - no special characters.</p>
  
  <p>wget -O - -q -t 1 '<a href="https://www.DOMAIN.org/sites/all/modules/civicrm/bin/cron.php?name=USERNAME&amp;pass=PASSWORD&amp;key=KEY" rel="nofollow noreferrer">https://www.DOMAIN.org/sites/all/modules/civicrm/bin/cron.php?name=USERNAME&amp;pass=PASSWORD&amp;key=KEY</a>'</p>
  
  <p><a href="https://i.sstatic.net/6b3GV.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6b3GV.jpg" alt="Cron screenshot"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-06-21T23:27:14.607Z
Comments.Text: Have you tried another cron job, something simple like a script that adds 2+2 and get the result?  Do you have shell access there and can you shell in and try your wget command from the commandline?  And finally, when is the last time you got an email (the cron job should send you an email if it's running)?
Comments.UserDisplayName: Lesley Evensen
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-06-22T21:15:28.480Z
Comments.Text: I wanted to add that if your cron job is being run, you (the admin) should be getting an email every time the cron runs.  If there's an error you'd still get the email; if no email, seems cron isn't running.
Comments.UserDisplayName: Lesley Evensen
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-06-23T03:30:59.527Z
Comments.Text: No emails. Just noticed another account is having the same problem. So I guess I will put this on hold for the moment, as we're in the middle of migrating to a newer server. Then if it doesn't run there, I'll ask the webhost for help since no one has pointed to any issues with the format of the cron.
Comments.UserDisplayName: Jenni Simonis
Tags: <cron><scheduled-job>
Title: Scheduled jobs cron not working properly
ThreadText: # Scheduled jobs cron not working properly
  
  (Asked by: username_0 on 2017-06-21)
  
  We use CPanel to run crons on our sites. The cron had been working fine and then stopped some months back. I've tried every example I can find, but it still is not running properly.
  
  I've attached a screenshot of what the cron looks like in CPanel as well as the cron in text (redacted to remove personal info). The username, password, and key are all letters/numbers - no special characters.
  
  wget -O - -q -t 1 '<https://www.DOMAIN.org/sites/all/modules/civicrm/bin/cron.php?name=USERNAME&pass=PASSWORD&key=KEY>'
  
  [![Cron screenshot](https://i.sstatic.net/6b3GV.jpg)](https://i.sstatic.net/6b3GV.jpg)
  
  **Tags:** cron, scheduled-job
  
  > **Comments:**
  > **username_1**: Have you tried another cron job, something simple like a script that adds 2+2 and get the result?  Do you have shell access there and can you shell in and try your wget command from the commandline?  And finally, when is the last time you got an email (the cron job should send you an email if it's running)?  
  > **username_1**: I wanted to add that if your cron job is being run, you (the admin) should be getting an email every time the cron runs.  If there's an error you'd still get the email; if no email, seems cron isn't running.  
  > **username_0**: No emails. Just noticed another account is having the same problem. So I guess I will put this on hold for the moment, as we're in the middle of migrating to a newer server. Then if it doesn't run there, I'll ask the webhost for help since no one has pointed to any issues with the format of the cron.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2017-12-20. Score: 1
  
  Since you're using a `wget`-based cron, there should be a corresponding entry in the web server log for each cron run. Look to see the Apache value - does it return `404` or `500` or maybe something else? `404` would indicate a wrong URL; `403` would indicate it's blocked, perhaps because of the user agent (iThemes Security for WordPress does this in its default configuration). A `200` or `500` would mean to check the CiviCRM log in ConfigAndLog.
  
  
  ---
  
  ### Answer by username_3 on 2017-06-22. Score: 0
  
  I had an issue like this once. The cron was being run by logging in with a username and password and the password for that user had changed so the cron was not able to access properly.
  
  > **Comments:**
  > **username_0**: Nope, the password is correct. I'm the only one who has access to the users. I even went and copied the password from the cron and made sure it was the same for the user. It was. Username is correct as well. Has full CiviCRM priviledges.  
  
  ---
  
  