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

Could not connect to the MariaDB - MySQL database

You will want to verify you are using the correct database name, username and password. All...

Changing Maximum Upload Size

Firts check your control panel for the "PHP Options" icon. If available you can change the PHP...

Running a PHP file with a cron job

To run a PHP file from cron, use the "cron jobs" section of your control panel. Use the following...

Internal Server Error with PHPList

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

Register Globals On

If you run a script that requires php "register globals on" create a php.ini file and include the...