Ian Spurgeon Posted August 4, 2018 Share Posted August 4, 2018 I have just installed PrestaShop on my hosting platform, clicked on the link to the admin to start setting it up and it returned with '500 Internal Server error' Link to comment Share on other sites More sharing options...
selectshop.at Posted August 4, 2018 Share Posted August 4, 2018 1) Read server error logs. 500 errors are internal server error logs. 2) probably your server is not fulfilling min. requirements to road Prestashop. Finde here tested in production requirements PS 1.7. -> https://www.prestashop.com/forums/topic/633857-server-requirements-for-ps-17/ PS 1.6. -> https://www.prestashop.com/forums/topic/633856-server-requirements-tested-in-production-for-ps-16/ 3) activate debug mode: https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/ Link to comment Share on other sites More sharing options...
jetx Posted August 6, 2018 Share Posted August 6, 2018 The other issue (if 1.7.4.2 or earlier versions) is directory and file permissions, depending upon your servers umask settings. If it's sloppy (like most) then it will probably work, but if your seeing server 500's after an installation then that is the first thing I would check. Link to comment Share on other sites More sharing options...
selectshop.at Posted August 6, 2018 Share Posted August 6, 2018 @Jetx - yes you are right. Latest PS versions are having several right problems, although on latest 1.7.4.2 this should be already debugged. And let me say this is also a problem with latest OS versions. Seems they for ex. made changes from Utunbu 14.04. to 16.04 and again to 18.04. and 19.04. On one of my old servers (Ubuntu 14.04.) I had no problems with permissions, but suddenly with same configuration and upgrade to 16.04. The complete new 18.04. showed than same permissions problems, so it is not only Prestashop fault. Link to comment Share on other sites More sharing options...
Ian Spurgeon Posted August 6, 2018 Author Share Posted August 6, 2018 This is what the hosting company came back to me with FYI Base on the error logs, it's the .htaccess that causes the error. So I've renamed the .htaccess file and it appears to have worked now. Can you double check. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now