HI,
emamarro wrote:Operating system Linux
Kernel version 2.6.17.11-grsechg
Apache version 1.3.37 (Unix)
PERL version 5.8.7
PHP version 4.4.4
MySQL version 4.1.21-standard
cPanel Build 10.9.0-CURRENT 39
Theme cPanel X v2.6.0
This is really an up-to-date machine
The
Premature end of script headers means that Apache crashes while processing the PMF home index.php page. In theory there is no big differences between what coded in the admin/index.php page (and you said that you're able to access and run the backend) and that in the home index.php. The debug will be hard: first we need to be assured that if mod_security is running in you server its
SecFilterDefaultAction has a status error different from 500 (my guess is yes, unfortunately).
Usually such errors needs direct root access to the server in order to be debugged: this is clearly impossible, being your account a customer one and the server shared.
So, waiting for a reply about the HTTP status used by mod_security, the only way for debugging this Apache crash is:
- Remove the PMF htaccess file, if you've renamed it from _.htaccess to .htaccess;
- Find out where the script ends using several exit(); to discover the block of code that crashes your Apache child
- Analize that code in order to make some questions to your hoster
To perform this rough debug you need to insert this line:
starting from the begin of the page, tipically between two block of codes (see the blank lines: e.g. line # 25, 30, 34, 40, ...) and hit the page until you'll see your current error page: that will be the "wrong" block of code for your server.
Sorry, but this is the only way for finding out what's wrong in PMF for your server: my personal experience within the WHM/CPanel context is that your hoster has included some wrong modules in the last PHP/Apache recompiling update but we need to be sure of this hypothesis.
Ciao,
Matteo