Unable to upload images

I noticed that after rebooting my server that the problem went away. This leads me to believe that it’s a cache issue.

Possibly the first attempt gets hung up and repeated tries is still referencing the same file in cache. If you don’t have access to reboot your machine then try renaming the file or logging back in to an incognito session.

I was experiencing this problem (browser console was returning 413 Request Entity Too Large). I looked at my Nginx error log and saw “client intended to send too large body.”

I fixed it (for my situation) by increasing client_max_body_size in /etc/nginx.conf to something more sane… client_max_body_size 16M;

@mdknight – I noticed that when I cURL your site, it is returning the “Server: nginx/1.16.0” header.

• This reply was modified 4 years, 9 months ago by Daniel Hendricks. Reason: Fixed WP editor non-standard markdown syntax

I’m running Nginx with PHP 7.4 on an Ubuntu 18.04 VPS.

Temporarily fixed the issue by downgrading from PHP 7.4 to PHP 7.3

Hi, we must downgrade? This will be fixed soon?

Hi, we must downgrade?

No.

This will be fixed soon?

Is that a question or a statement? It is not broken. It is a misconfiguration. It will be fixed as soon as you configure it correctly.

I’m running Nginx with PHP 7.4 on an Ubuntu 18.04 VPS.

Me too.

I fixed it by increasing client_max_body_size in /etc/nginx.conf to something more sane: client_max_body_size 16M;

> Is that a question or a statement? It is not broken. It is a misconfiguration. It will be fixed as soon as you configure it correctly.

Why I need to configure something if 5.3.2 version won’t work and older versions work? It’s clearly a bug or something devs have not considered before 5.3.2 release.

I fixed it by increasing client_max_body_size in /etc/nginx.conf to something more sane: client_max_body_size 16M;

I’ve got client_max_body_size 100M;

This started after I switched to PHP 7.4

Also, I’m seeing that others have this issue when running with PHP 7.3, and fixing by switching to PHP 7.2. While I’m doing PHP 7.4 -> PHP 7.3.

I don’t have any theories, as I’m not sure what’s going on. Just figured I’d pitch in with my solution and what I’m noticing.

Guys, for all people having this issue. I solved it by doing the following steps:

– Delete WP cache in case you are using it (WP cache, W3 total cache, etc…)
– Delete CDN cache in case you are using it (Cloudflare and similar)
– Delete Browser cache
– Go to Menu –> Media Library –> Add New
– DO NOT drag and drop. Press the “select files” button” and upload
– Done!

I hope it works for you.

Just came across the same bug. I tried the following proposed solutions:

• Clearing cache
• Changing PHP versions
• Uploading via Media library
• Using add_filter( 'big_image_size_threshold', '__return_false' );

Nothing worked. The image uploads, but I still get the error and can only see the image in the library after re-loading the page.

• This reply was modified 4 years, 9 months ago by Alex Kladov. Reason: fixed formatting problems

I agree with Cs

> Is that a question or a statement? It is not broken. It is a misconfiguration. It will be fixed as soon as you configure it correctly.

Why I need to configure something if 5.3.2 version won’t work and older versions work? It’s clearly a bug or something devs have not considered before 5.3.2 release.

All this trial and error stuff makes it look like this is a users’s problem. It is not.

I had this same problem, it was doing my head in.

MY SOLUTION
Check the file name to make sure there is no apostrophe in it.

I am having the same issue but it is intermittent with say 2 images out of many on a bulk upload showing the error, despite all of my images only being 1280 wide.

Only thing has change for me is updating to WP 5.3.2 – Putting server on PHP 7.4 while also changing PHP image processing module from gmagick to imagick. I have changed back to Gmagick and will report on if that fixes it?

Failing that will roll back PHP, failing that will roll back WordPress to an earlier version.

I rolled back to WP 5.2.5 and still got an HTTP error, so I looked up solutions for that and adding “SetEnv MAGICK_THREAD_LIMIT 1” to the htaccess file worked – from here: https://www.wpbeginner.com/wp-tutorials/how-to-fix-the-http-image-upload-error-in-wordpress/ Scroll down to #4.

I had previously tried the plugin mentioned earlier in this thread, downgrading PHP version, among other things. Nothing worked until now. Hope this helps someone!

I struggled with this for a while but wanted to share what I did to fix it.

I was receiving the “async-upload.php” error in my browser console mentioned in the beginning of this thread. After trying almost every fix in the thread, I remembered seeing something about apache. This led me to check my apache logs which pointed me in the right direction:

[Wed Feb 12 13:29:34.636401 2020] [ssl:error] [pid 12207:tid 140213057730304] [client xxx.xx.xxx.xx:0] AH02018: request body exceeds maximum size (131072) for SSL buffer, referer: https://xxxxx.com/wp-admin/upload.php
[Wed Feb 12 13:29:34.654627 2020] [ssl:error] [pid 12207:tid 140213057730304] [client xxx.xx.xxx.xx:0] AH02257: could not buffer message body to allow SSL renegotiation to proceed, referer: https://xxxxxx.com/wp-admin/upload.php

After removing the SSL certificate and reinstalling it (auto SSL) I am not able to upload images successfully.

Hope this helps!

Mine worked AFTER I saved the post. Once I saved the post, the edit would let me drag media back into it without error.