 |
|
Server
Updates |
500 Internal Server Errors?
By design, CGI has a few simple security features built into it. If a file is breaking these rules, you will receive a "500 Internal Server Error". Some examples of an Internal Server Error are as follows. - If a file or directory is writable by others, it will produce an error since this would be an insecure execution of the file. - PHP values in your htaccess files are not supported, you must put your custom PHP settings in a php.ini file, or else you will receive an error. - If your account is using over 25 processes, 100MB or more per PHP thread, or exceeds a 30 second execution time, you will receive an Internal Server Error. Being that this is a relatively big change, we understand that not every user may know how to change the correct permissions or modify their htaccess files accordingly. To assist with the migration, we have created an automated program that will convert the htaccess files and file permissions on your account to the appropriate settings for PHPSuEXEC. We have taken most situations into consideration; however, this script might not be perfect for every script. This being the case, our support technicians will be delighted to assist you with any issues you encounter. Why are we switching to PHPSuEXEC? When the majority of the Media Hosting's servers were commissioned, the administration at that time felt that mod_php was the more sensible choice. Now that Media Hosting has grown and promoted new members to their administrative team the current consensus is that PHPSuEXEC would be the better of the two choices. This decision was made, in part, because mod_php is less secure in shared environments. If you have questions please contact us. |
Server
Downtime Explanations: • As noted. Data centers are up and functioning completely!
Current local time: |
