Answers.Body: <p>So I resolved the issue. Here's what I found. It looks like the permissions for <strong>bin</strong> have changed from <strong>755</strong> to <strong>775</strong> at some point (I looked at one of our backups and it used to be 755, but in 4.7.29 it was set to 775.)</p>
  
  <p>I used this question and response:
  <a href="https://civicrm.stackexchange.com/questions/19989/url-for-cron-jobs-gives-me-a-404-error/20004">URL for cron Jobs gives me a 404 error</a> (not the same error, but I was desperately searching!)</p>
  
  <p>Made the same changes (<strong>updated bin permissions to 755</strong>) and it all worked. So that's good (for now) but with every upgrade will we have to remember to update permissions?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-01-18T05:45:17.523Z
Answers.LastActivityDate: 2018-01-18T05:45:17.523Z
Answers.UserDisplayName: Jane
Body: <p>I upgraded our test site to 4.7.29 (type fixed) yesterday and the cron has been failing since then with a 500 server error.</p>
  
  <p>We are running on Wordpress 4.9.2. The cron has been working successfully until now for years.</p>
  
  <p>We have a cron job running every 30 minutes using the URL to cron.php method.
  I've checked the cron.php permissions; they haven't changed and have checked that the user and password are still valid and have enough permission (they do). When I run the command directly from the command line I also get a 500 internal server error, same with running it in a browser. The only thing we did was upgrade the version of CiviCRM.
  Help?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-17T20:41:20.777Z
Comments.Text: Try upgrading it to 4.7.29 .
Comments.UserDisplayName: Pradeep Nayak
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-17T22:25:12.970Z
Comments.Text: Can you paste the error log please.
Comments.UserDisplayName: Hassan Farooq
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-01-18T04:44:52.170Z
Comments.Text: Sorry - that was a typo. It is version 4.7.29
Comments.UserDisplayName: Jane
Tags: <cron><scheduled-job>
Title: Upgrade to 4.7.29 causes Internal Server Error with cron
ThreadText: # Upgrade to 4.7.29 causes Internal Server Error with cron
  
  (Asked by: username_0 on 2018-01-17)
  
  I upgraded our test site to 4.7.29 (type fixed) yesterday and the cron has been failing since then with a 500 server error.
  
  We are running on Wordpress 4.9.2. The cron has been working successfully until now for years.
  
  We have a cron job running every 30 minutes using the URL to cron.php method.
  I've checked the cron.php permissions; they haven't changed and have checked that the user and password are still valid and have enough permission (they do). When I run the command directly from the command line I also get a 500 internal server error, same with running it in a browser. The only thing we did was upgrade the version of CiviCRM.
  Help?
  
  **Tags:** cron, scheduled-job
  
  > **Comments:**
  > **username_1**: Try upgrading it to 4.7.29 .  
  > **username_2**: Can you paste the error log please.  
  > **username_0**: Sorry - that was a typo. It is version 4.7.29  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-01-18. Score: 1
  
  So I resolved the issue. Here's what I found. It looks like the permissions for **bin** have changed from **755** to **775** at some point (I looked at one of our backups and it used to be 755, but in 4.7.29 it was set to 775.)
  
  I used this question and response:
  [URL for cron Jobs gives me a 404 error](https://civicrm.stackexchange.com/questions/19989/url-for-cron-jobs-gives-me-a-404-error/20004) (not the same error, but I was desperately searching!)
  
  Made the same changes (**updated bin permissions to 755**) and it all worked. So that's good (for now) but with every upgrade will we have to remember to update permissions?
  
  
  ---
  
  