My Directory site is showing a blank page or Internal server error frequently

We’ve had a customers in general have an issue where their site is showing a blank page or 500 Internal server error frequently. All of them were using GoDaddy server.

We generally recommend users to use Site5 hosting to run the template without having such an issue(s) as Directory is an application like theme so it is natural that it will require more server resources then other simple WordPress themes and as soon as your site gets traction both content and traffic on your website will increase simultaneously so your website will need more server resources for better performance.

If you are on a shared hosting your server resources will be shared with other websites on the same server so you will get limited resources for your website which will ultimately result in an underperforming website. On the other hand if you go with a dedicated server all server resources will be available for your website and it will perform much better.

However, if you would like to go with GoDaddy server, here is a list of some solutions which you should try to resolve the issue:

Solution – 1:

First of all, check the PHP version you are using. It should be 5.5 or greater.

You can refer to this link for how to update the PHP version:

https://www.godaddy.com/help/view-or-change-your-php-version-3937

Solution – 2:

Check your site’s error log. You can ask your web host for the error log. If you are getting the error mentioned below in your error log, then follow these steps:

Error: Connection reset by peer: mod_fcgid: error reading data from FastCGI server

Steps:

  • Go to /home/sitename/fcgi-bin
  • Use this command to reset the immutable flag: chattr -i php5.fcgi
  • Then delete the /home/sitename/etc and /home/sitename/fcgi-bin directories (making sure that anything that’s not PHP related in etc is saved)
  • Using virtualmin switch back to apache mod_php mode and then back to FCGId mode. The site should now work. Don’t forget to chow any files/directories in public_html that were apache to : Note that these are both usually the sitename.

If you guys are not aware about the steps mentioned above, then consult with your web host regarding this as they would be better able to help you resolve this matter.