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

How can I view/modify data in my MariaDB - MySQL database?

Only make changes if you know exactly what you are doing. Often incorrect changes can have an...

How can I run PHP5?

PHP5 is now the default PHP ran on our servers. Nothing further is required.

Learn MariaDB

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

What is the path to PHP5?

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

When trying to connect to MariaDB or MySQL you receive error 2003 Cannot connect to MySQL on x.x.x.x on port 3306 (10060)

Please ensure you have added the remote IP to the allow list in your hosting control panel...