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.

  • 129 Users Found This Useful

Was this answer helpful?

Related Articles

How do I backup a MariaDB - MySQL Database?

In the control panel, within Backup section, under Download a SQL Database Backup will be your...

Learn MariaDB

MariaDB is a drop-in replacement for MySQL. The lead developer and founder of MySQL, Michael...

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...

What is the path to PHP5?

We are currently running the latest stable version of PHP5. /usr/bin/php

What is the Path to ImageMagick?

The path to ImageMagick is /usr/bin/