Support » Localhost Installs » The server cannot process the image. This can happen if the server is busy or do

  • I am running the latest version of WordPress on a self installation (Ubuntu) and noticed that I always see this error with certain images I have yet to find a solution. I have increased Memory Limit to 256M in php and also Maximum upload file size to 1 GB and no luck.

    The server cannot process the image. This can happen if the server is busy or does not have enough resources to complete the task. Uploading a smaller image may help. Suggested maximum size is 2560 pixels.

    Again, things I have tried:

    • Memory Limit increased to 256M
    • Maximum upload file size to 1 GB
    • Renaming the file to test.jpg
    • Verifying the file size (currently testing a JPG at 1.1M)

    I ran out of things to try. Any ideas?

Viewing 5 replies - 16 through 20 (of 20 total)
  • unzilasiddique

    (@unzilasiddique)

    been facing the same issue on my admin user. funny thing is that we have gone through all solutions mentioned online like increasing the server limit, upload size, clear cache etc. also, this error comes up for my user specifically. images are uploading fine on other’s end.

    Change your WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT in your wp-config.php and php.ini. I had it at 512M when started showing the error, then I changed it to 256M ! It’s Working perfect again. ALL GOOD!!!

    Setting the memory_limit to a very high value might be an issue too, this limit is also protecting your server by blocking inefficient PHP code. If you allocate too much memory, and there are poorly coded scripts, it might be counterproductive because your server could start eating into disk swap space.

    https://docs.wp-rocket.me/article/128-increase-php-memory-limit-in-wordpress

    Had the same problem with a very small image, 1700×300 px, ~47Kb size.

    I only changed the WP_MEMORY_LIMIT to 256, refreshed the page, and it worked.

    Strangely, I’ve had this limit in my wp_config.php file, but I commented out at some point in time. Unfortunately, I don’t remember why… I hope it doesn’t have a negative impact in other areas.

    I had the same problem and the solution was to rename the file. There was a name with an apostrophe that generated that error about the size that had nothing to do with it.

    This just randomly becomes a problem today. I’ve done thousands of websites and this is the first time I’ve seen this flag happen when it was a compressed image that is below the threshold.

    Had to clear the cache to get rid of the issue.

Viewing 5 replies - 16 through 20 (of 20 total)
  • You must be logged in to reply to this topic.