June 6, 2014 06:09 by ben
Every time that a 500 Internal Server Error occurs, you should take the guidance in that error literally: You should contact the system administrator of the hosting environment to report the real error to you. Internally something went wrong, and as long as the real error is not fetched, everybody will be clueless.
These types of problems specifically occur in hosting environments that use some kind of CGI-interface to PHP (CGI, FCCGI, FastCGI, suPHP). It could be that something went wrong on the configuration-level, but it might also be that PHP encountered some kind of PHP Fatal Error. In all cases, fetching the actual log from the logfiles is vital. Note that - unless you have root-privileges - it is likely that you don't have access to these log-files. Therefor, contact the hosting provider.
Here are the three most common reasons why you found 500 Internal Server Error:
1. File permissons set incorrectly.
One common cause for a 500 Internal Server Error are the file permissions of PHP-scripts. In general, all files for MageBridge should have the same file permissions as the other Joomla! files and/or Magento files. A 500-error might be thrown if the file permissions are considered to be dangerous: The execution bit should never be used on PHP-files (755 or 777 or something alike), but some servers also object against the PHP-file being world-writable (666 or 777). File permissions like these can be set either through SSH or FTP.
Another common cause of PHP Fatal Errors that again might generate Internal Server Errors, is that the PHP memory limit (memory_limit) is too low. You should make sure your Joomla! site meet up with the minimum requirements of MageBridge.
How you should modify the PHP configuration accordingly, again depends on the hosting environment and you should contact your hosting provider about this. It might be that you can add PHP-directives to your htaccess-files, but it might also be that you need a separate php.ini file somewhere.
2. Leaving file permissions set incorrectly after manual installation of content management systems, forums, blogs, etc.
3. Coding errors in the .htaccess file.
The best and most easy way to detect error 500 is to check out the error reporting that is generated by your website:
1. Log in to the administrator back end in Joomla and than go to the Global configuration option.
2. Than select server tab
3. got to the error reporting option
4. Change this to maximum to get full version
5. click on save button
To track down what is causing the error, you will want to start with the error log in Control Panel. Once you are logged into your Control Panel look for and click on the "Error Log" icon under "Logs."
log_errors = On
error_reporting = E_ALL & ~E_DEPRECATED
display_errors = On
Host Your Joomla Site with ASPHostPortal.com
What makes ASPHostPortal.com the premier place to hosting Joomla? Here are 5 reasons why we are the best:
Easy to Use Tools
ASPHostPortal.com use World Class Plesk Control Panel that help you with single-click Joomla installation.
Best Programming Support
ASPHostPortal.com hosting servers come ready with the latest PHP version. You can get access directly to your MySQL from our world class Plesk Control Panel.
Best Server Technology
The minimal specs of our servers includes Intel Xeon Dual Core Processor, RAID-10 protected hard disk space with minimum 8 GB RAM. You dont need to worry about the speed of your site.
Best and Friendly Support
Our customer support will help you 24 hours a day, 7 days a week and 365 days a year to assist you.
Uptime & Support Guarantees
We are so confident in our hosting services we will not only provide you with a 30 days money back guarantee, but also we give you a 99.9% uptime guarantee.