Premature end of script headers

If you receive an Internal Server Error 500 and checking your log files displays "Premature end of script headers" errors this can occur for a couple reasons.

This can represent a permission issue. If using PHP be sure to set your .php files to 755 with our service.

Coding Issue: You have an extra space or carriage return in your coding after the closing of the ?php tag.

Your script has exceeded resource usage limits. This can occur if your script is using over 128MBs in a single process. After the 128MB the process is killed due to excessive resource usage which results in the internal server error and a premature end of script headers listing in the error logs. To prevent this from occurring you will want to optimize your coding to be more efficient and use less memory via optimization, reducing features, pruning databases, or upgrading your plan to a plan better suited to the high memory demands your account requires such as the semi-dedicated plan or higher.


Share this page:


Was this article useful? Have any suggestions or improvements to the information?

Also Read

Learn MySQL

If you do not know how to use MySQL there are some great guides at the following websites....

What port is MariaDB - MySQL on?

MariaDB / MySQL is on Port 3306.      

Strict Standards: Non-static method JLoader::register() should not be called statically in...

This error indicates your script is using out-dated PHP commands. It is best to update your...

Warning: system() has been disabled for security reasons

system is a feature of php which is disabled by default. To change this if needed for a...

Internal Server Error with PHPList

PHPList produces internal server error. Checking error logs results in: Invalid command...