Fresh Install/Upgrade: Unable to Access Install

[12toes]

Howdy!

Help, please.

This is a fresh install through Fantastico ver. 1.3.0.1. The install called for an upgrade to 1.3.0.2. Now that I've upgraded, I can not access zc_install to patch the DB. I can't access it straight http, nor https.

I've tried changing .htaccess to no avail, tried with and without comments. I've pasted the changes/results below. I've removed partial file info/paths, the .htaccess resides the zc_install directory.

I hope someone can point me in the right direction.


.htaccess file:
<IfModule mod_security.c>
SecFilterEngine On
SecFilterScanPOST On
</IfModule>

## If for some reason the above doesn't produce the desired results, simply remove the # from the
## following lines:
SecFilterEngine On
SecFilterScanPOST On

error:
File does not exist:/public_html/500.shtml
/public_html/shoppe/zc_install/.htaccess: SecFilterEngine not allowed here


.htaccess file:
<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

## If for some reason the above doesn't produce the desired results, simply remove the # from the
## following lines:
SecFilterEngine off
SecFilterScanPOST Off

error:
File does not exist: /public_html/500.shtml
/public_html/shoppe/zc_install/.htaccess: SecFilterEngine not allowed here

TIA!

[DrByte]

How about removing the zc_install/.htaccess file altogether. That should get rid of the problem.

[12toes]

Thanks. No, it didn't work.

[DrByte]

okay, so when you remove it, what is the new error?

[12toes]

duh! Sorry!

File does not exist: /woggit/public_html/500.shtml
Premature end of script headers: /public_html/shoppe/zc_install/index.php

[12toes]

bump.

still can't access the zc_installer.

thanks.

[12toes]

Just wanted to say Thanks! Issue was resolved by hosting company. I'm trying to find out what they did/didn't do to resolve it.

I appreciate your time!

[DrByte]

It was most likely a mod_security conflict.

The supplied .htaccess attempts to temporarily override mod_security protections due to some agressive coding methods used in the installer which mod_security doesn't like very well.

However, since your host was preventing you from overriding its settings, the installer couldn't proceed. I suspect they simply altered their rules for your domain to let the code proceed.

[12toes]

aaaah. Veddy intelestinghk! Thanks for the explaination...'cause they ain't givin' away their mojo! That's especially fine by me since it's related to security.

Thanks again, for both this excellent and well maintained software, and your assistance.

Have a terrific day!