lozaria Posted October 8, 2018 Share Posted October 8, 2018 Hello, I feel ridiculous, but I'm getting 500 error on two different hosting companies while trying to install Prestashop 1.7.4.3 and 1.7.4.2 The error log is: [Mon Oct 08 13:11:48 2018] [warn-ioncube] mmap cache can't open /home/..../var/cache/prod/appParameters.php - Permission denied I tried the suggestions regarding this type of error: I made 777 permissions on /var and /cache directory including subdirectories and files. I tried to use United States settings during the installation. But still without success. Link to comment Share on other sites More sharing options...
prestawal Posted October 10, 2018 Share Posted October 10, 2018 Hi, Sorry, I have no solution and I'm getting 500 errors on two different hosting companies while trying to install Prestashop 1.7.4.3 and 1.7.4.2 , too. In 1 case, the install process stops with an error. With the other hosting, the front works well but the I can't make the admin work. Just error 500. Now I know about the renaming of the admin dir. But that part doesnt work very well. Tried PHP 5.4, 7.0 and 7.1. It makes no difference. Enough memory. Enough script exc time. Uploaded the zip file and index. Uploaded the complete unzipped Prestashop, too. Changed languages on different occasions. But after about 12 times trying to install it I am out of ideas. Changed permissions to 755, too. I do get it fully installed however, admin dir renamed automatically in the end, on my local Xampp. Link to comment Share on other sites More sharing options...
jstillings1 Posted October 13, 2018 Share Posted October 13, 2018 (edited) I know the answer to this.. but your gonna hate it. Cpanel has a bug with PHP-FPM it is not able to allow Prestashop the php requirements it needs. I have been thru 5 hosts all cpanel and whm. I did not even get this installed until I bought a Plesk server. The 500 error is solvable but the 403 afterwards is not. This will not always be the issue if you can wait it out do so. CPanel is aware of the PHP-FPM bug and is aiming to fix BUT they are still resistant against allowing one of the switchs needed for prestashop to work to be on the PHP-FPM control panel. Those two variables marked in red are impossible right now to set correctly for Prestashop on a cpanel whm setup due to their bug. http://prntscr.com/l5joad The really kick a__ thing about the bug is if your on shared hosting and you set a custom php.ini to match prestashop rules it will screw up everyone on your shared hostings php! FUN! IT Hosting support people love when ya do that. Call them and tell them what you did they will love to fix the other 3 containers by breaking yours! Edited October 13, 2018 by jstillings1 (see edit history) Link to comment Share on other sites More sharing options...
musicmaster Posted October 14, 2018 Share Posted October 14, 2018 When you have a 500 error always enable development mode: https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/ Usually it is some php or mysql error Link to comment Share on other sites More sharing options...
prestawal Posted October 18, 2018 Share Posted October 18, 2018 Hi, Thank you for your help and advise. Since I cant access the back end, I set debugging to True in '_PS_MODE_DEV_', This does not give any extra information. It just says: ---Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. --- So, it recognises the page. Otherwise it would have thrown a 404. The access log only says HTTP 500. But no further information on why or what. The Hosting admin only tells me there has been a PHP WARN. A script took longer then 5 minutes to execute. max_execution_time and max_input_time are 120 secs. Cant go any longer with the Hosting I am on. Assigned memory is 256 M. allow_url_fopen = ON Yes, this is on shared hosting... Tried installing 1.6 first and updating to 1.7. But that doesn't work because of the server error jqXHR using 1-click upgrade. It probably is some php or mysql error. Link to comment Share on other sites More sharing options...
goundiam Posted October 19, 2018 Share Posted October 19, 2018 I get the same error, and wheh I check the logs, here is what is given: PHP message: PHP Warning: Invalid argument supplied for foreach() in ../classes/shop/Shop.php on line 347" while reading response header from upstream, If it's a bug without no solution for the moment, which version of prestashop does support php-fpm correctly ? Link to comment Share on other sites More sharing options...
prestawal Posted October 23, 2018 Share Posted October 23, 2018 Hi, In my case, the problem was solved. The admin folder has it's own htaccess file. In this file, the Multiviews Options were blocked out: <IfModule mod_negotiation.c> #Options -MultiViews </IfModule> This did the trick. I can access the admin pages now. Thanks to the the people of the shared hosting. They helped me out here. Link to comment Share on other sites More sharing options...
oli becof Posted March 6, 2021 Share Posted March 6, 2021 i had same problem , my got solved by closing the database page what i accessed in the background.. Link to comment Share on other sites More sharing options...
olehdj Posted March 28, 2022 Share Posted March 28, 2022 Add in domain --> Hosting y DNS --> Configuration --> Apache y nginx add in directive aditionals nginx: gzip_proxied any; gzip on; gzip_http_version 1.1; gzip_vary on; gzip_comp_level 6; gzip_proxied any; gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript application/javascript text/x-js; gzip_buffers 16 8k; gzip_disable «MSIE [1-6].(?!.*SV1)»; add_header Strict-Transport-Security «max-age=15768000» always; client_header_buffer_size 16k; large_client_header_buffers 16 16k; proxy_buffers 16 16k; proxy_buffer_size 32k; fastcgi_buffer_size 32k; fastcgi_buffers 16 12k; 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