LemonStand Documentation

Troubleshooting a 500 Internal Server Error after installation

On some hosting environments you can face a Internal Error 500 after installation. There could be different reasons of this issue, but all of them are caused by the non-conformity between the hosting settings and LemonStand requirements. Here are some hints:

  • Check whether the mod_rewrite Apache module is enabled on your hosting server. Usually the module is enabled on all modern paid hosting servers.
  • Check whether the AllowOverride All option is enabled in the httpd.conf file for the LemonStand directory. Usually the option is enabled on CPanel-based hostings for all directories.
  • Try to uncomment the following line in the .htaccess file in the LemonStand root directory: 
    # RewriteBase /
    If this will not help, please comment the line again.
  • Look into the Apache error log. If you use a CPanel-based hosting, you can access the error log via the CPanel Logs/Error Log page. Find errors which refer to the LemonStand installation directory. They can help you to find the problem.
  • If the error log contains the following message "SoftException in Application.cpp:252: File "your_lemonstand_dir/index.php" is writeable by group", change permissions on the index.php file to 755. Also please change the FILE_PERMISSIONS parameter value in the config.php file to 0755: 
    $CONFIG['FILE_PERMISSIONS'] = 0755;
  • Try chmod 755 on your index.php. If that doesn't work try 775.
  • If nothing helps, contact our support team. Please send us the Apache error messages if it is possible.

Next: Troubleshooting image and file uploading issues
Previous: Installing LemonStand using the web installer
Return to Installing LemonStand

Comments

+ Add a comment

Regan Shepherd

Friday, October 29, 2010

Changing the permissions on the index.php file to 755 fixes this error with MediaTemple on Dedicated-Virtual accounts.

Ben Wells

Thursday, April 21, 2011

@Regan Shepherd
That worked on HostGator servers too. Thanks!!!

Trey Copeland

Saturday, April 23, 2011

Yes, changing index.php to 755 works for me.

David Cole

Monday, November 28, 2011

I didn't get this error on an older installation of Lemonstand on Cpanel, but I did get the error on a new installation of Lemonstand on a newer version of CPanel. I think the most likely cause is that default configuration is different in newer versions of Cpanel, or perhaps this particular web host configures CPanel a little differently.

Changing index.php permissions to 755 and changing file_permissions in config.php to 0755 seemed to do the trick. Fingers crossed it all goes super smoothly from here in.

Add your comment

Loading form...