As with any platform, in that location are e'er those annoying errors or issues you lot accept to learn how to piece of work through. Trust us, we've pretty much seen them all! From the white screen of death to database connection errors, WordPress definitely has its quirks. 😉 Just we yet love information technology! Today we're going to dive into ane of the more common ones, theHTTP error. Users typically meet this when trying to upload images or videos to the WordPress media library.

While the HTTP mistake is usually like shooting fish in a barrel to fix it tin be rather frustrating as it ordinarily interrupts your workflow. Goose egg is worse than spending 20 minutes trying to find that perfect epitome for your weblog post, y'all go to upload it, and bam, you lot're suddenly met with a very vague error.

Below nosotros'll explore why this fault happens and what you can do to rapidly resolve it and then y'all tin can go dorsum to uploading your media.

What is the WordPress HTTP Error?

The WordPress HTTP mistake occurs when something goes incorrect while attempting to upload images or videos using the built-in media library tool. Unfortunately, different browser errors where nosotros can usually reference an HTTP condition code, WordPress errors are sometimes a little harder to troubleshoot (especially if you don't know how to enable WordPress debugging mode).

The very vague "HTTP mistake" definitely doesn't aid you determine what might be wrong or fifty-fifty where to commencement looking. Just that is because at that place could be a few causes for the failure and WordPress simply doesn't know why, so it spits out a generic mistake message (equally seen below).

WordPress HTTP error when uploading images
WordPress HTTP error when uploading images

How to Fix the WordPress HTTP Error

From our experience, the WordPress HTTP error typically originates from two things: the kickoff is acustomer-side or user error (your login session, bad characters in the file proper name, etc.), and the second is atrouble or setting on your WordPress host(server issue, memory list, tertiary-party plugin, shared hosting throttling resources, etc.). And then nosotros'll swoop into a little of both.

Hither are some recommendations and things to check to fix the error (sorted in gild by well-nigh common reasons we see):

  1. Refresh the Page
  2. Compress or Resize the File
  3. Rename the Prototype File
  4. Temporarily Conciliate Plugins and Theme
  5. Ask Your WordPress Host
  6. Increment PHP Memory Limit
  7. Bank check Uploads Folder Permissions
  8. Motility to the Latest Version of PHP
  9. Fix Functioning Bug with Imagick and Shared Hosts
  10. Remove Custom Media Library Path
  11. Disable mod_security
  12. Install the Add together To Server Plugin

ane. Refresh the Page

The very first thing you lot should do when encountering the WordPress HTTP fault is to only refresh the page in your browser. Sounds too easy correct? 😉 Well, really this is the virtually mutual fix we've seen for information technology. Here's why:

First, for whatever reason, your browser might have lost connection temporarily with WordPress and the procedure just failed to complete. This could exist due to your ISP, a temporary hiccup with your WordPress host, etc. If you refresh the page and try uploading again it the fault sometimes will resolve itself.

Second, nosotros've also seen that sometimes subsequently refreshing the page, or coming back to the WordPress editor from another tab, that information technology suddenly kicks yous out. This is most likely an indicator that your WordPress login session has expired. Yous should see the post-obit message:

Your session has expired. Please log in to continue where you left off.

Your session has expired
Your session has expired

So naturally, you lot log back in and try to upload your media again. Nonetheless, the HTTP fault occurs. This is kind of a quirk with WordPress. Once you log back in, y'all demand to really manually refresh the folio you're on. So uploading media volition piece of work again.

2. Compress or Resize the File

You might need to edit your prototype file, which could entail reducing the file size (KB or MB) or decreasing the width/pinnacle (pixels). We recommend checking out our in-depth mail on how to optimize images for the web. In that location are a lot of third-political party image optimization plugins you lot can use to automatically do this for y'all (both reducing and resizing) when your paradigm is uploaded to the media library.

We have used Imagify on our Kinsta site for years without a single outcome. But there are a lot of other bully ones out there as well. Just make sure whichever plugin you employ, that they are optimizing images on their own servers, not locally. If yous're bulk optimizing images locally this can drastically harm your site's functioning.

Imagify WordPress plugin
Imagify WordPress plugin

It's OK to upload loftier-resolution images as WordPress supports responsive images out of the box. In fact, you volition probably desire to so that the image looks crisp on retina displays. But unless your a photographer or business concern that needs high-resolution images a adept rule of thumb though is to keep your last image size nether 100 KB and no more than than double the size of your website'due south content div width.

As well, you might have to play with the PNG and JPG file types. Sometimes one tin be much larger than the other depending on what type of epitome it is.

Depending on the configuration of your WordPress host, you might likewise want to expect into increasing the WordPress maximum upload file size.

3. Rename the Image File

Information technology can never hurt to endeavour and rename the epitome file. WordPress should automatically append a number on the cease if y'all try to upload a duplicate file name, but in case that doesn't work, endeavor renaming your file. Unfortunately, WordPress doesn't permit you lot rename the file of an already uploaded image file, then you will need to rename it locally and re-upload it.

When we are uploading images that already be nosotros typically add a -1 or -two on the end (case: epitome-file-1.png, image-file-ii.png). Make sure to add the dash otherwise Google will read it as i word and it could hurt your SEO.

Also, to exist condom, stay articulate of uploading an image with file names that contain special characters. This includes international language symbols and characters such every bit apostrophes. Dashes are OK. You can encounter in this example beneath on the Kinsta Japanese site, we are using English language for the file names, not the special characters. While WordPress can technically support these, there are a lot of other problems that tin pop up.

Rename image file with no special characters
Rename image file with no special characters

iv. Temporarily Deactivate Plugins and Themes

It'due south always a good thought if you're having HTTP errors to try deactivating your plugins and even switch your WordPress theme to the default to encounter if this resolves the trouble. A few plugins that are are typical culprits include image optimization plugins (they tie direct into the media library) and security plugins such as WordFence (these plugins are sometimes too restrictive). Or you can only delete your WordPress theme.

If y'all don't desire to affect your alive site, just clone your live site to a staging surround. If the WordPress HTTP error is also happening on staging, then you can speedily deactivate all your plugins to start narrowing it down.

Retrieve, you won't lose any data if yous simply deactivate a plugin. If you lot can still access your admin, a quick way to do this is to browse to "Plugins" and select "Deactivate" from the bulk deportment carte du jour. This will disable all of your plugins.

Deactivate all plugins
Deactivate all plugins

If this fixes the issue y'all'll need to discover the culprit. Start activating them ane by one, and try uploading an image once more in the media library. When you see the HTTP error render, you've establish the misbehaving plugin. You can and then reach out to the plugin programmer for help or postal service a back up ticket in the WordPress repository.

If yous can't access WordPress admin you can FTP into your server and rename your plugins folder to something like plugins_old. And so check your site again. If it works, and then y'all volition demand to exam each plugin ane by one. Rename your plugin folder dorsum to plugins and then rename each plugin folder inside of if it, one by one, until yous find it. You could as well try to replicate this on a staging site kickoff.

Rename plugin folder
Rename plugin folder

The same goes for your WordPress theme. Typically themes don't necktie into the media library, but we've seen some weird setups. It never hurts to attempt switching your theme over to the default 20 Seventeen theme to see if information technology fixes it. Just like with plugins, you don't have to worry about losing your current theme settings. All of that is stored in the WordPress database.

v. Ask Your WordPress Host

If you've tried the steps above already and are nonetheless getting the WordPress HTTP mistake, nosotros recommend reaching out to your WordPress host for aid before proceeding. Many of the additional troubleshooting steps are a lilliputian more advanced and a lot of times you can ask your host to do or check on this for you.

Kinsta'south support team is bachelor 24×vii from the bottom right-hand side of the MyKinsta dashboard.

Kinsta WordPress hosting support
Kinsta WordPress hosting back up

half-dozen. Increase PHP Memory Limit

Another cause for the WordPress HTTP error is that your server lacks the bachelor memory for the background upload process to complete successfully. This is a very common problem with shared WordPress hosting. To set information technology y'all demand to increase the amount of retentiveness PHP tin apply.256 MB is recommended.

The default memory limit for Kinsta clients is already prepare to 256 MB. If you host your WordPress site at Kinsta yous shouldn't have any issues with a lack of memory. 👍

Increase PHP Memory Limit with wp-config.php

You tin increase the PHP memory limit past calculation the following lawmaking to your wp-config.php file. Note: this may exist overwritten past a server-level dominion in place past your WordPress host.

          define( 'WP_MEMORY_LIMIT', '256M' );        

Increase PHP Memory Limit in cPanel

If your host is using cPanel, you can increment the PHP memory limit in two different areas.

The first is under the software section. Click on "Select PHP Version." Click on "Switch to PHP Options." You can then click on "memory_limit" to modify its value.

The second area is also under the software section. Click on the "MultiPHP INI Editor" tool. This allows you to modify the php.ini file. Just scroll down to where it says "memory_limit" and input a higher value.

Increase PHP memory limit in cPanel
Increase PHP memory limit in cPanel

Increment PHP Memory Limit with php.ini

Subscribe Now

If you lot aren't using cPanel, y'all can also edit the php.ini file direct if you take access. To do this, login to your site via FTP or SSH, become to your site's root directory and open or create a php.ini file.

Tin can't connect via SSH? Larn how to ready the SSH "Connection Refused" fault.

If the file was already there, search for the "memory_limit" setting and change information technology every bit necessary.

Some shared hosts might likewise require that you add the suPHP directive in your .htaccess file for the higher up php.ini file settings to work. To do this, edit your .htaccess file, also located at the root of your site, and add the post-obit lawmaking towards the pinnacle of the file:

          <IfModule mod_suphp.c>  suPHP_ConfigPath /abode/yourusername/public_html </IfModule>        

Increment PHP Memory Limit with .htaccess

The .htaccess file is a special hidden file that contains various settings you tin employ to change the server behavior, right downward to a directory specific level. If you don't have access to php.ini, we advise you effort this next. Starting time, login to your site via FTP or SSH, have a look at your root directory and see if there is a .htaccess file there.

If there is yous can edit that file to and modify the "php_value memory_limit" value.

vii. Cheque Uploads Folder Permissions

Typically when there is a folder permissions error you should get a message in WordPress about it not existence able to write to the directory. However, this might not always be the case. If a WordPress site has been hacked or infected with malware, there could be a lot of issues going on with the permissions.

Tip: Kinsta offers costless hack fixes for all clients. 😄

The primary binder you're concerned with is your /wp-content/uploads folder, equally this is where files are stored when uploaded via the media library.

According to the WordPress Codex, all directories should be 755 (drwxr-xr-x) or 750.

You tin easily see your folder permissions with an FTP client (every bit seen below). You could also reach out to your WordPress host support team and ask them to quickly GREP file permissions on your folders and files to ensure they're prepare properly.

Make sure that if yous manually update the permissions on this folder that you check both the "Recurse into subdirectories" option likewise as the "Use to directories just."

WordPress uploads directory permissions
WordPress uploads directory permissions

eight. Motility to the Latest Version of PHP

WordPress officially recommends PHP vii.3 or higher. If y'all're not running on that, y'all're beneath the minimum requirements set by the developers of the CMS. 😮

Nosotros always recommend running the latest and supported versions of PHP due to the fact it offers better security and performance, including problems fixes and functions that need to be deprecated.

We have seen older versions of PHP contribute to all sorts of errors, including the infamous WordPress HTTP mistake. At Kinsta you tin easily modify to PHP 7.four with a single click in the MyKinsta dashboard.

Change to PHP 7.4
Change to PHP 7.four

If your host uses cPanel they might already have an option available to you to modify your version of PHP. Simply log in to cPanel and nether the "Software" category click on "Select PHP Version."

Select PHP version
Select PHP version

You tin then select the PHP versions available to yous that your host supports.

php 7 cpanel
PHP vii in cPanel

nine. Fix Performance Bug with Imagick and Shared Hosts

There are 2 different PHP modules WordPress uses for image processing: GD Library and Imagick (ImageMagick). Depending on what is installed on your server, WordPress may use either ane.

The problem is that shared WordPress hosts have a lot of hidden resource throttling behind the scenes. That is the merely way they tin cram then many users on the same automobile. A common issue people run into is that at that place are too few resources allocated to Imagick (ImageMagick). Hosts will limit the power to use multiple threads, hence resulting in the WordPress HTTP fault.

Y'all can add the post-obit code to the top of your .htaccess file, irresolute the thread limit value to something higher.

MAGICK_THREAD_LIMIT one

Another selection you take is to tell WordPress to use the GD library instead of Imagick. You can practise this by only adding the post-obit code to your theme's functions.php file.

          function wpb_image_editor_default_to_gd( $editors ) { $gd_editor = 'WP_Image_Editor_GD'; $editors = array_diff( $editors, array( $gd_editor ) ); array_unshift( $editors, $gd_editor ); render $editors; } add_filter( 'wp_image_editors', 'wpb_image_editor_default_to_gd' );        

We'll exist blunt. If y'all're having to tweak things like this it's time to move to a new WordPress host. Kinsta doesn't have crazy limits like this in place and for the nearly part, yous're only limited by PHP workers. You shouldn't take to worry near these types of things as a website owner.

Nosotros utilize LXD managed hosts and orchestrated LXC software containers for each site. What this ways is that every WordPress site is housed in its own isolated container, which has all of the software resources required to run information technology (Linux, Nginx, PHP, MySQL). The resources are 100% individual and are not shared between anyone else or fifty-fifty your own sites.

Read more well-nigh how Kinsta is different than any other host yous've tried.

10. Remove Custom Media Library Path

It very well could exist that your media library path isn't setup correctly. We typically meet this when users migrate their local development site over to production. If you look in "Media" under "Settings" in your WordPress dashboard and come across a file path value listed, go ahead and delete information technology and click "Relieve Changes." Y'all want your media to be stored in the default /wp-content/uploads folder.

Below is what it typically looks similar. If yous don't run into a library path, then you're all practiced here.

WordPress media settings
WordPress media settings

11. Disable mod_security

Mod_security is an open source firewall that sometimes might crusade the WordPress HTTP error to occur. You lot tin can disable mod_security by adding the following code to the meridian of your .htaccess file.

<IfModule mod_security.c> SecFilterEngine Off SecFilterScanPOST Off </IfModule>

If you're using cPanel, you can likewise disable it by clicking into "ModSecurity" in the "Security" section.

cPanel ModSecurity
cPanel ModSecurity

Then toggle the status from "On" to "Off" side by side to the domain you want to disable it on.

Disable mod_security
Disable mod_security

Nosotros ever recommend using an enterprise-form and yet affordable WAF like Sucuri or Cloudflare instead. You can read our recommendation for the all-time WAF settings here.

12. Install the Add From Server Plugin

Terminal but not least, if you're really in a demark and nothing else seems to exist working, you lot can install the free Add together From Server plugin. Perhaps you lot're waiting for a response from your WordPress host or a developer on how to become the WordPress HTTP error resolved.

Add From Server WordPress plugin
Add From Server WordPress plugin

The Add to Server plugin will usually get you effectually the error and could be a good temporarily set up, specially if y'all're right in the eye of something important. Information technology was originally developed to allow you to add very large files via SFTP.Of import: this plugin is no longer maintained or supported. Use at your ain risk.

Summary

As you can see there are quite a few different ways to ready the WordPress HTTP mistake. Hopefully one of the solutions above worked for you lot and you're already dorsum on track and uploading your media. If you go along to receive this error time and time over again, it might be time to consider upgrading to a ameliorate WordPress host. Many of the solutions above are things you lot don't have to worry about at Kinsta.

If you establish a solution that isn't in our listing, please leave a comment a below and we'll become it added.


Save time, costs and maximize site performance with:

  • Instant help from WordPress hosting experts, 24/vii.
  • Cloudflare Enterprise integration.
  • Global audience attain with 29 data centers worldwide.
  • Optimization with our built-in Application Performance Monitoring.

All of that and much more, in one program with no long-term contracts, assisted migrations, and a 30-day-money-dorsum-guarantee. Cheque out our plans or talk to sales to find the plan that'due south correct for yous.