Title: server error 500 inside wp-includes
Last modified: September 15, 2018

---

# server error 500 inside wp-includes

 *  [smallstar67](https://wordpress.org/support/users/smallstar67/)
 * (@smallstar67)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/)
 * This is an ongoing problem we had noticed since we have started a daily close
   watch in Google search console. Every few months search console will throw us
   50-80 500 server errors listed inside “wp-includes” The first few times we thought
   it was our server even though we could find nothing wrong and no programs or 
   plugins were added or deleted. In a few days, normally after a wordpress, or 
   another plugin like woocommerce had updates, we would see all the server errors
   disappear. We would ask google search console to re index and the whole process
   starts over again and each time there was no clear reason as to why the errors
   were there to begin with or how they were fixed.
    We have attached a screen shot
   of one of the errors. It seems to be generally inside: /wp-includes/widgets /
   wp-includes/customize/ /wp-includes/SimplePie/
 * Has anyone seen this type of behavior and does it seem like it’s related to the
   theme?
    We are using Generate press Premium version 1.6.2
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fserver-error-500-inside-wp-includes%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 6 replies - 1 through 6 (of 6 total)

 *  Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/)
 * (@sterndata)
 * Volunteer Forum Moderator
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10691258)
 * That’s where the error is being detected, in all probability.
 * Errors like this are logged. Check the error log on your server. If you can’t
   find the log, please contact your host.
 * Meantime, enable wp_debug and wp_debug_log and after an error, look at wp-content/
   debug.log to see if anything gets logged there. [https://codex.wordpress.org/Debugging_in_WordPress](https://codex.wordpress.org/Debugging_in_WordPress)
 * You can also try this: Please attempt to disable all plugins, and use one of 
   the default (Twenty*) themes. If the problem goes away, enable them one by one
   to identify the source of your troubles.
 *  Thread Starter [smallstar67](https://wordpress.org/support/users/smallstar67/)
 * (@smallstar67)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10691332)
 * We run our own VPS at the WHM level, so unless something is actually wrong with
   the server, this seems to be our problem. The error logs in these directories
   don’t seem to tell us much. Here is example of the error log for the “wp-includes/
   SimplePie” directory, the only error log is from june 26th, yet the 500 error
   seems to have started in the last few days:
 * [25-Jun-2018 16:10:41 UTC] PHP Fatal error: Class ‘SimplePie’ not found in /home/
   usanunch/public_html/wp-includes/SimplePie/Core.php on line 55
    [26-Jun-2018 
   09:33:04 UTC] PHP Fatal error: Class ‘SimplePie’ not found in /home/usanunch/
   public_html/wp-includes/SimplePie/Core.php on line 55 [26-Jun-2018 11:23:16 UTC]
   PHP Fatal error: Class ‘SimplePie’ not found in /home/usanunch/public_html/wp-
   includes/SimplePie/Core.php on line 55 [26-Jun-2018 14:34:06 UTC] PHP Fatal error:
   Class ‘SimplePie’ not found in /home/usanunch/public_html/wp-includes/SimplePie/
   Core.php on line 55
 * If you go to line 55 in the Core.php file in this directory, the file consists
   of four lines of code:
 * class SimplePie_Core extends SimplePie
    {
 * }
 *  Thread Starter [smallstar67](https://wordpress.org/support/users/smallstar67/)
 * (@smallstar67)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10691373)
 * Error_log in /wp-content/ listed this:
 * [14-Feb-2017 07:50:49 UTC] PHP Warning: file_put_contents(/home/usanunch/public_html/
   wp-content/languages/mo.php): failed to open stream: No such file or directory
   in /home/usanunch/public_html/wp-content/index.php on line 19
    [15-Feb-2017 06:
   41:28 UTC] PHP Warning: file_put_contents(/home/usanunch/public_html/wp-content/
   languages/mo.php): failed to open stream: No such file or directory in /home/
   usanunch/public_html/wp-content/index.php on line 19 [13-Apr-2017 01:17:46 UTC]
   PHP Warning: file_put_contents(/home/usanunch/public_html/wp-content/languages/
   mo.php): failed to open stream: No such file or directory in /home/usanunch/public_html/
   wp-content/index.php on line 19 [15-Aug-2017 03:12:13 UTC] PHP Warning: file_put_contents(/
   home/usanunch/public_html/wp-content/languages/mo.php): failed to open stream:
   No such file or directory in /home/usanunch/public_html/wp-content/index.php 
   on line 19
 *  Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/)
 * (@sterndata)
 * Volunteer Forum Moderator
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10691786)
 * It looks like you’re missing some core files.
 * If you can get to DASHBOARD->UPDATES, click the button to reinstall the current
   version of WordPress.
 *  Thread Starter [smallstar67](https://wordpress.org/support/users/smallstar67/)
 * (@smallstar67)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10697515)
 * We have run the re install but it doesn’t change anything. Since this post we
   started checking other sites on different servers, some with fresh same day WP
   installs with no plugins installed, and we found that all sites display these
   errors when trying to browse these PHP files.
    The new running idea is that these
   files aren’t meant to be indexed, or shown individually and that google doesn’t
   normally index them, but for some reason they did index ours (one suggestion 
   was that an index file was somehow placed in the wp-includes directory and it
   was “scraped”) We have been advised to modify our robot.txt file to exclude the
   wp-includes directory but we are afraid that we will be penalized by google for
   blocking the resource.
 *  Moderator [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/)
 * (@sterndata)
 * Volunteer Forum Moderator
 * [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10697528)
 * There’s nothing in wp-includes that google needs to index.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘server error 500 inside wp-includes’ is closed to new replies.

## Tags

 * [500 error](https://wordpress.org/support/topic-tag/500-error/)
 * [index](https://wordpress.org/support/topic-tag/index/)
 * [wp-includes](https://wordpress.org/support/topic-tag/wp-includes/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 6 replies
 * 2 participants
 * Last reply from: [Steven Stern (sterndata)](https://wordpress.org/support/users/sterndata/)
 * Last activity: [7 years, 8 months ago](https://wordpress.org/support/topic/server-error-500-inside-wp-includes/#post-10697528)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
