Home > Computer > Fix WordPress Not Acceptable Error 406

Fix WordPress Not Acceptable Error 406

Posted By Raymond In Category: Computer

Aug
12
2006
Donate

I’ve been able to publish new articles on my blog and sometimes I do save them up before publishing for editing/updating it later.
For no reason, I was unable to save an article which I was working on. When I click on Save and Continue Editing button on my WordPress, I get the “Error 406, Not Acceptable. An appropriate representation of the requested resource /wp-admin/post.php could not be found on this server.”
Wordpress 406 Not Acceptable post.php
I tried writing a new article with any random story and this time was able to save!
I looked around for what could be causing this problem and I found the problem with solution…

It seems that this Error 406 is caused by your webhost and it has nothing to do with you. The mod-security rules that were installed for the server security would have caused the issue. ModSecurity is an open source web application firewall.
To fix this problem, you can either contact your webhost and ask them to fix the rules from the mod_security.. or you can try the fix below which worked for me.


At the root of your blog, locate the file .htaccess and add a line “SecFilterEngine off” without the quotes.
For example, the root of my blog is http://www.raymond.cc/blog/. There should be a .htaccess file at that location.
Another easier way to do it is login to your wp-admin, navigate to Manage -> Files.
You will see Recent and Common in bold on your right hand side. At Common, click on “.htaccess (for rewrite rules)”.
Add the line “SecFilterEngine off” without quotes and click on the Update File button.

You should no longer get the “Error 406, Not Acceptable. An appropriate representation of the requested resource /wp-admin/post.php could not be found on this server.” error.


Related posts:
  • MSN Messenger 7.5.0319 QFE Patch (80048820 error FIX)
  • MSN Messenger Error 80048820
  • Google 502 Server Error
  • MSN Messenger 7.5.0320 QFE Patch (80048820 error FIX)
  • Nasty Spam on WordPress Comment box
    • http://www.watblog.com rajiv

      thanks man!!! your solution really helped!!!

    • http://www.wongkeenhing.com Justin Wong

      Works like a charm. Thanks dude.

    • farking

      beware..if u set it off..you website no longer under mod_security protection… :)

    • William Chen

      thx, worked!

    • http://www.codyhess.com Cody

      Thanks for the 411! Big help.

    • pnreddy

      Good job ..It worked…

      You saved me lot of time…

    • http://kikay.exchange.ph gary

      thanks a lot man. helped me too. you might wanna note that in order for the .htaccess file to be editable on WP’s admin area it needs to be editable.

    • Pingback: Jason Friesen {dot} ca » Blog Archive » New Flock and 406 Errors

    • Pingback: “Problem Loading Page” » editing CMS error 406 Not Acceptable

    • Abdul Rahman

      Work great! Thanks a lot!

    • http://knits.wifetalks.com Rayne

      Thanks a bunch! This worked perfectly.

    • Pingback: Accepted! at neollene.com

    • http://randomstupid.com steve

      great… half an hour of prose… lost, thanks to this error .

      now i can’t even download that file … time to switch this puppy off

    • http://republikbabi.com Calvin Michel Sidjaja

      Does it work for wordpress 2.3.3? I’ve been encountering this problem after I change my permalink structure, or when I moved my domain to 000webhost.com. I don’t know which caused what because I haven’t bothered to edit my post since I moved it recently.

      Anyway, is the final result supposed to be like this?

      # BEGIN WordPress

      SecFilterEngine off
      RewriteEngine On
      RewriteBase /
      RewriteCond %{REQUEST_FILENAME} !-f
      RewriteCond %{REQUEST_FILENAME} !-d
      RewriteRule . /index.php [L]

      # END WordPress

      I saved it like that and it gave me horrifying 500 Internal server error instead. For now, I could edit my post with semagic, but still, it’s not really comfortable and more limited compared to wp gui.

    • james

      Your host has mod_security enabled for a reason. Most hosts have filters that will prevent commonly known exploits against your php scripts. Disabling mod_security on your entire account would leave you vulnerable.

      You should disable mod_security for the file only with this code in your .htaccess file:

      secfilterengine off

    • http://www.iluvdesi.com notrick

      @Calvin Michel Sidjaja

      Its better to use this

      SecFilterEngine Off
      SecFilterScanPOST Off

    • http://republikbabi.com Calvin Michel Sidjaja

      @notrick
      apparently the problem happens because I use 000webhost.com, they ban these following keywords: rapidshare, megaupload, filefactory, etc. The best solution is, don\’t use these keywords if your host ban them.

    • http://www.reversecellphonesearch.biz Jason

      Wow, this really worked. You saved me a lot of time!

      Thanks.

    • http://tech.shantanugoel.com Shantanu Goel

      With Mod security 2, this is no longer valid. I\’ve written about it and a workaround at
      http://tech.shantanugoel.com/2008/05/01/http-406-errors-galore.html

    • Coisox

      apparently the problem happens because I use 000webhost.com, they ban these following keywords: rapidshare, megaupload, filefactory, etc. The best solution is, don\\’t use these keywords if your host ban them.
      Thx Calvin Michel Sidjaja! I host at 000webhost. I use the word RapidShare. One of my article list down free file hosting and image hosting services to save bandwidth for free webhosting.

    • Michael

      As a webhost, I’d like to chime in on this issue. This is indeed caused by mod_security, however, simply disabling mod_security isn’t an ideal solution. To that end, I’d like to provide the syntax for shutting off just this one rule.

      For servers running mod_sec 1, it’s SecFilterRemove 300040. For servers running mod_sec 2, it’s SecRuleRemoveById 300040.

      YMMV, as there may be more than one rule that is causing the problem, but any decent webhost should be more than willing to find the rule number in the mod_security audit.log file and turn the one rule off. After all, if they’re running mod_security in the first place, they would seem to have your interests, or at least a lack of desire to fix a problem caused by not having it, at heart and thus motivation to solve the problem for you.

    • Patrick

      great, that worked fine for me!

    • http://www.johntanyishin.com johntanyishin

      That’s a great help!

      WordPress is so difficult to some people, at least for me.

      Thanks!

      JTYS

    • http://Help,please? TR

      Could somebody explain this to me like I’m a 5-year-old please?

      I don’t know where this “htaccess” file lives. I go to my WordPress Dashboard and see no “files” category under “Manage”. Everyone seems to love this solution and I would love to love it also. Please help me to share in the joy?

    • tnx

      It’s working! Thank you.

    • http://huhe.blogspot.com Joe He

      Thanks for your solution. It works!

    • Jeremy

      thanks

    • http://www.deepvoidlog.com DeepVoid

      I don’t have words to thank you!!! You really helped me a lot, you can’t imagine how much important is this fix for me! I’m about to delivery an important work for a major customer, and this recurrent problem was a true nightmare for me. Again, THANK YOU!!! :-)

    • http://enyong.com oner

      Anyway thanks.. its works..
      Thanks very much…. I searching every where about this error.

    • Patrickv

      This does not work for me, I’ve tried. Downloaded the HTaccess file but apparently it’s empty. and even adding these lines, does not help. any more ideas ?

    • http://www.idesign.ph web-devel

      Thanks, this works for me,.:D

    Copyright © 2005-2012 - Raymond.CC Blog