Multisite subdomain image upload HTTP error

  • Resolved llparker

    (@llparker)


    11 years, 2 months ago

    We’ve been running a WordPress multisite for a long time. We have a freshly-rebuilt subdomain install on a self-hosted Ubuntu 14.04.1, Apache 2.4 server, and until late December, the Media Uploader worked fine for all of our blogs. Since about January 1st, 2015, our blog Media Uploaders don’t work anymore–neither with the multiple file uploader nor the browser uploader.

    With the multiple file uploader interface, we get a generic “HTTP error” that my browser debugger (Chrome) flags as these two errors:

    “Failed to load resource: the server responded with a status of 500 (Internal Server Error) http://chemicalbilology.scientopia.org/wp-admin/async-upload.php

    Failed to load resource: net::ERR_CACHE_MISS http://chemicalbilology.scientopia.org/wp-admin/media-new.php”

    The file DOES upload, and goes to the correct folder in the subdomain file structure, but it does not get resized/converted into the other versions (crunched) as normal, and it won’t attach properly from the Media Library if used in a post.

    The main site uploader, from the “Site 1” blog, works fine–files upload and crunch successfully.

    We’ve already set our file upload limits on the server site to be very high, and permissions are all appropriate. Nothing changed on our end at all from the time that it did work until when we found it wasn’t working anymore. I’ve Googled all over to try to find out what is going on, and this doesn’t seem to be coming from any of the previously discussed sources (permissions, plugins, PHP settings). It could be an .htaccess problem, I suppose, and our .htaccess file is quite complex because of a custom set of weird rewrites we had to do because we changed from subdirectory to subdomain with the fresh install. But that .htaccess file has been working fine since the new version went live in October 2014, and this problem has only appeared as of late December 2014/early January 2015.

    I am stuck!!!!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    11 years, 2 months ago

    That means that ImageMagick isn’t able to run. Do you have any mod_security type protection on your server?

    Normally I’d say to start with the /tmp folder and make sure it’s not full but since the main site works, that seems unlikely.

    Thread Starter llparker

    (@llparker)

    11 years, 2 months ago

    Thanks for replying–we are not running mod_security, we have an ip-tables firewall (which I think serves a similar purpose…our server is set up on Linode and I just followed all the linode documentation for the LAMP setup, which includes securing via ip-tables), but that hasn’t changed between when it used to work and when it stopped working.

    I checked that we have ImageMagick installed, and we do (and, the main site working implies that in principle ImageMagick is functional).

    Could it be a rewrite rule problem with how ImageMagick figures out where the files are for crunching? That’s the only thing I can think of, like maybe it’s having trouble finding the initially uploaded files? But if so, how would I find what is causing that in the first place? 🙁

    Thread Starter llparker

    (@llparker)

    11 years, 2 months ago

    Okay–I just solved the problem, after finding this thread with the potential solution in comment #11: https://wordpress.org/support/topic/media-upload-error-wordpress-40?replies=12

    We use WP Super Cache, and I went into the settings and clicked “Delete cache from all blogs” and now it works again.

    I’m still not sure why the cache was blocking image crunching, and also, simply disabling WP Super Cache was not sufficient to solve the problem (because I tried disabling all plugins to no avail), but there we go.

    To future admins with this problem–try deleting the cache from all blogs on your WP Super Cache. 🙂

    Thread Starter llparker

    (@llparker)

    11 years, 2 months ago

    AAAAARRRGGHH nevermind. It worked for a day, and now doesn’t work anymore. And the cache delete trick did not work again.

    Back to the drawing board…

    Thread Starter llparker

    (@llparker)

    11 years, 2 months ago

    Okay–so, I resolved the problem again–this time I deactivated and then deleted the Sucuri plugin and it started working again.

    I do not know why for sure… except that possibly it had something to do with the combination of the Easy WP SMTP plugin we have on our multisite and the attempts that Sucuri makes to send “Media file added” emails to the blog’s owner. We did not have anything in each individual blog’s Easy WP SMTP configuration, only the main network site (which did work), so there were errors in the PHP log for Sucuri trying to email blog owners according to their WP account emails and failing.

    I may at some point test out setting up each blog with the Easy WP SMTP config details, and see if that enables them to work together and allow image uploads. I like Sucuri but it doesn’t seem essential for us–it mostly was useful as a gauge of just how much bruteforce password guessing goes on at our site–A LOT. But, fingers crossed, no break-ins yet anyway.

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

The topic ‘Multisite subdomain image upload HTTP error’ is closed to new replies.