Hey esmi,
I tried the .htaccess trick and this plugin but both didn’t work. Either just one of them or in combination…
get this, the other admin on my site can upload from a safari browser, but I can’t from Firefox or i.e 9
I have tried every fecking different fix there is on here, as far as I see its a coding bug thats been present for years now, wp need to sort it out
I’m getting the same error now as well. Crazy part is this WAS working one hour ago. Nothing has changed other than I’m trying to add new content.
This is suddenly happening to me as well. I look forward to hearing what solutions there might be
Just to add to the randomness:
I am using WP 3.2.1 on a Windows XP system and Firefox 3.6.23. When uploading images I get the red HTTP error the first attempt, but if I try a second time it works. This error was occurring randomly before, but now it seems to have settled in to doing it every time.
I just tried the image uploader in IE8 and it worked great the first time. So more and more this is looking like a browser + Flash issue.
I am having the same issue “RED HTTP ERROR” I even tried to FTP the images into the uploads folder and they will not show up in the library. Has anyone figured this out yet? I have a bunch of other wordpress installs and there is no errors but this one blog is producing it.
I have the same problem since a day ago. Images are uploading and appearing in the library, but the images can’t be crunched!! Tried the htacces, several plugins, but nothing is helping. Is there any solution for this yet???
Ok, so I have seen TONS of these errors all over Google, but not one single person ever really explained what the REAL PROBLEM was. Some of the previous solutions work if you’re using .htaccess to password protect the directory — but many are not protecting their directories. Some of the previous solutions will work if you’re on Godaddy Hosting — but many are not on godaddy hosting, so fastcgi isn’t the problem. So what could be the main problem?
FOR ME, THIS WAS THE MAIN PROBLEM: mod_security
On Apache, mod_security BLACKLISTS ^Shockwave Flash at REQUEST_HEADERS:User-Agent. Nearly 99.9% of apache servers have this setup as default. This is what the flash uploader from wordpress uses as the user-agent when it’s being used.
This is a simple fix — just have your hosting company WHITELIST ^Shockwave Flash in mod_security. It’s blacklisted as a spambot by default — so if you change it (or your host does), you will no longer have this problem.
This is NOT a browser issue, not an OS issue, etc. It’s just being blacklisted, that’s all. Take note, servers upgrade their apache software (including mod_security) all the time — and the newer versions might overwrite your current rules. So if this happens again later on down the road, then you know you need to whitelist ^Shockwave Flash again (if and when you get that silly http error ever again.)
FYI: I discovered this because the http error is a 406 error, which is what made me look at the log files of mod_security. 406 errors should never really occur unless something is blacklisted.
Call your host or do it yourself if you have a dedicated server. Trust me, this should fix the problem if you’ve tried everything else and none of it worked. 🙂
Hey,
I have the same problem. But it just happens because my wordpress folder in cpanel is password protected. When I remove password protection, it works fine.
So check your wordpress installed directory and make sure it is not password protected.
I probably encountered the issue that you mentioned, ispyppc. Thanks for the post, though I made my own fix..
I noticed the html uploader was working fine, and so suspected it was OS-side and called the host. However 1and1 support didn’t have a clue and asked me to wait for further instructions via e-mail..
I am an impatient man, and too determined to quit at that. Thus I recently did this because I wanted to ensure that the uploader can’t use Flash anymore to circumvent the issue altogether. Besides, media.php was supposed to be turning off Flash when mod_security is enabled anyways; but it looks like the logic thereof generates a false positive even though it checks for that. ::rolls eyes::
My issues with uploads are gone now until the clients update WordPress. Maybe I will write a plug-in someday..for now the linked steps I wrote work fine for me.
