Forums / Install & configuration / 406 not acceptable error on install...

406 not acceptable error on install...

Author Message

wayne street

Monday 19 February 2007 10:09:50 am

I am installing on a sub-domain...

I uploaded all files to my host.

I then run the install wizard.
It came back with directories that I needed to chmod, so I did that.

It then progressed to outgoing email setup. I choose 'Sendmail/MTA' and hit next.

I then get:
406 not acceptable
An appropriate representation of the requested resource /index.php could not be found on this server.

I check and thee ez publish index.php file is in the subdomain root directory.

Any suggestions.

Claudia Kosny

Monday 19 February 2007 11:47:21 am

Hi Wayne

If you google around a bit you can find quite a few pages stating mod_security as the reason for this problem. The recommended solution is to add the following to your .htaccess:

<IfModule mod_security.c>
 SecFilterEngine Off
 SecFilterScanPOST Off
</IfModule>

Please note that I don't know whether doing this is a good idea as I don't have the slightest clue what mod_security is actually doing. On the other hand this htaccess addition was recommended for drupal, joomla, wordpress ... so if you want to use a cms it seems that you have to live with it.

Claudia

wayne street

Tuesday 20 February 2007 9:06:40 am

Thanks. That worked and got me a little further along.

Three Quarks

Wednesday 09 May 2007 1:45:15 am

check your error log for apache mine was error_log

you should see a mod_security error message

mine was
[Wed May 09 02:30:33 2007] [error] [client 210.209.74.203] mod_security: Access denied with code 406. Pattern match "!(/imp/login\\\\.php)" at HEADER("Referer") [id "300018"] [rev "3"] [msg "Generic PHP code injection protection via ARGS"] [severity "CRITICAL"] [hostname "www.somedomain.com"] [uri "/index.php?option=login"] [unique_id "gnZhgH8AAAEAAEa8QMAAAAAA"]

grepped 300018 in /etc/httpd/conf.d/ the id for the error message

found mod_sec-rules.conf had a matching rule

the rule was "really broad furl_fopen attack sig"

There are two version of this same rule.

Commented out the 1st version.

restarted httpd / apache.

error message no longer appeared.

Three Quarks

Wednesday 09 May 2007 2:52:45 am

quick update.

i rewrote the rule as follows:-

SecFilterSelective REQUEST_URI "!(/tiki-objectpermissions|aardvarkts/install/index|/do_command|banner_click|wp-login|tiki-view_cache|/horde/index|/horde/services/go|/goto|gallery2?/main|ad-?server/adjs)" "chain,id:300018,rev:3,severity:2,msg:'Generic PHP code injection protection via ARGS'"
SecFilterSelective REQUEST_URI "\.php(3|4|5)?(\?http|&http|\?ftp|&ftp)" chain
SecFilterSelective HTTP_Referer "!(/imp/login\.php)"

the original ARGS option was being ignored!