Why Failed to Open Stream Error Occurs?

Before we try to fix the error, it would be helpful to understand what causes the ‘Failed to open stream’ error in WordPress.

This error occurs when WordPress is unable to load the file mentioned in website code. When this error occurs, sometimes WordPress will continue loading the site and only show a warning message, while other times WordPress will show a fatal error and will not load anything else.

The message phrasing will be different depending on where the error occurs in the code and the reason for failure. It will also give you clues about what needs to be fixed.

Typically, this message would look something like this:

Warning: require(/home/website/wp-includes/load.php): failed to open stream: No such file or directory in /home/website/wp-settings.php on line 19 

Fatal error: require(): Failed opening required ‘/home/website/wp-includes/load.php’ (include_path=’.:/usr/share/php/:/usr/share/php5/’) in /home/website/wp-settings.php on line 19

Here is another example:

Last Error: 2018-04-04 14:52:13: (2) HTTP Error: Unable to connect: ‘fopen(compress.zlib://https://www.googleapis.com/analytics/v3/management/accounts/~all/webproperties/~all/profiles?start-index=1): failed to open stream: operation failed’

Having said that, let’s take a look at how to troubleshoot and fix ‘failed to open stream’ error in WordPress.

Fixing Failed to Open Stream Error in WordPress

As we mentioned earlier, the error can be caused by a variety of reasons and the error message will be different depending on the cause and location of the file that’s causing the error.

In each instance, failed to open stream phrase would be followed by a reason. For example, permission denied, no such file or directory, operation failed, and more.

Now if your error message contains ‘no such file or directory’, then you need to look in the code to figure out which file is mentioned at that particular line.

If it is a plugin or theme file, then this means that the plugin or theme files were either deleted or not installed correctly. Simply deactivate and reinstall the theme / plugin in question to fix the error.

However, it is also possible that WordPress is unable to locate the files because of a missing .htaccess file in your root folder. In that case, you need to go to Settings » Permalinks page in your WordPress admin and just click on the ‘Save changes’ button to regenerate the .htaccess file.

If the error message is followed by ‘Permission denied’, then this means that WordPress does not have the right permission to access the file or directory referenced in the code.

To fix this, you need to check WordPress files and directory permissions and correct them if needed.

Lastly, some WordPress plugins load scripts from third-party sources like Google Analytics, Facebook APIs, Google Maps, and other third-party APIs.

Some of these APIs may require authentication or may have changed the way developers can access them. A failure to authenticate or incorrect access method will result in WordPress failing to open the required files.

To fix this, you will need to contact the plugin author for support. They will be able to help you fix the error.

If none of these tips help you resolve the issue, then follow the steps mentioned in our WordPress troubleshooting guide. This step by step guide will help you pinpoint the issue, so you can easily find the solution.

We hope this article helped you fix the WordPress ‘failed to open stream’ error. You may also want to bookmark our list of the most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Fix the WordPress Failed to Open Stream Error appeared first on WPBeginner.

What Causes WordPress 429 Too Many Requests Error?

The most common reason for the 429 too many requests error is when a user, bot, or a script tries to make too many requests to the servers. It is a measure to prevent DDOS attacks on websites.

However if it is not properly configured, then it may end up preventing search engines or other APIs to run properly. This would cause unexpected behavior on your website.

Sometimes the error is caused when a script on your website is making too many requests to another website or service using an API. In that case, the API would respond back with a 429 error code.

That being said, let’s take a look at how to easily troubleshoot and fix 429 too many requests error in WordPress.

Fixing 429 Too Many Requests Error in WordPress

This error can be caused by a number of factors. We will show you multiple ways to troubleshoot and fix the 429 too many request error.

Find and Deactivate Misbehaving Plugin

The most common culprit of 429 error is usually a bad plugin on your website. Plugins can sometimes make subsequent requests to your website which may be rejected by the server with a 429 error code.

First thing you need to do is deactivate all WordPress plugins on your website. You can do this by visiting the plugins page in your WordPress admin area and selecting all plugins. After that, select ‘Deactivate’ under the bulk actions drop box and click apply.

If you are unable to access the WordPress admin area, then see our guide on how to deactivate all WordPress plugins via FTP.

Now check your website again to see if you can reproduce the 429 too many requests error again. If you can’t, then this means a plugin was causing this issue.

You can now turn on your plugins one by one and check your website after activating each plugin. This way you will be able to find the plugin causing the error.

Once you find the plugin causing the error, you can replace it with an alternative plugin or try reaching out to the plugin author to let them know about the error.

Switch to a Default WordPress Theme

More and more WordPress themes include functionality that normally comes with plugins. Such themes may also cause 429 error too many requests on your website.

The easiest way to find out is by switching to a default WordPress theme like Twenty Seventeen. If this resolves the 429 error issue, then you can find another WordPress theme or report the problem to the theme developer and they may be able to fix it.

Ask Your Hosting Provider

A lot of times, you will see a 429 too many requests error in third-party services that need access to your website. This could be search engines, crawlers, and other web apps.

If you are seeing the error in Google Search console or any third-party service, then most likely they are sending too many requests to your website. In that case, you need to ask your WordPress hosting provider to not block those requests.

We hope this article helped you fix the WordPress 429 error too many requests on your website. You may also want to see our list of most common WordPress errors and how to fix them.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Fix the WordPress 429 Too Many Requests Error appeared first on WPBeginner.