Forum archive
Turnkey Prestashop (Proxmox) unable to upgrade or install themes.
Hi. Some Prestashop 1.7.6.5 modules, such as one-click upgrade, return '500 server error' and any theme install from zip returns '500 internal' and prevents further access to themes page. Is this due to Proxmox default of running unprivileged container? I tried to restart privileged, but then the container fails to load apache process.
journalctl snippet:
Oct 13 05:46:15 test-shop systemd[259]: mariadb.service: Failed to set up mount namespacing: Permission denied
Oct 13 05:46:15 test-shop systemd[259]: mariadb.service: Failed at step NAMESPACE spawning /usr/bin/install: Permission denied
Oct 13 05:46:15 test-shop systemd[1]: mariadb.service: Control process exited, code=exited, status=226/NAMESPACE
Oct 13 05:46:15 test-shop systemd[1]: mariadb.service: Failed with result 'exit-code'.
Oct 13 05:46:15 test-shop systemd[1]: Failed to start MariaDB 10.3.22 database server.
Oct 13 05:46:15 test-shop systemd[258]: stunnel4@shellinabox.service: Failed to set up mount namespacing: Permission denied
Oct 13 05:46:15 test-shop systemd[257]: apache2.service: Failed to set up mount namespacing: Permission denied
Oct 13 05:46:15 test-shop systemd[257]: apache2.service: Failed at step NAMESPACE spawning /usr/sbin/apachectl: Permission denied
Oct 13 05:46:15 test-shop systemd[258]: stunnel4@shellinabox.service: Failed at step NAMESPACE spawning /usr/bin/stunnel4: Permission denied
Oct 13 05:46:15 test-shop systemd[1]: apache2.service: Control process exited, code=exited, status=226/NAMESPACE
Oct 13 05:46:15 test-shop systemd[1]: apache2.service: Failed with result 'exit-code'.
Oct 13 05:46:15 test-shop systemd[1]: Failed to start The Apache HTTP Server.
Oct 13 05:46:15 test-shop systemd[256]: stunnel4@webmin.service: Failed to set up mount namespacing: Permission denied
Oct 13 05:46:15 test-shop systemd[256]: stunnel4@webmin.service: Failed at step NAMESPACE spawning /usr/bin/stunnel4: Permission denied
Oct 13 05:46:15 test-shop systemd[1]: stunnel4@shellinabox.service: Control process exited, code=exited, status=226/NAMESPACE
Oct 13 05:46:15 test-shop systemd[1]: stunnel4@shellinabox.service: Failed with result 'exit-code'.
Oct 13 05:46:15 test-shop systemd[1]: Failed to start Universal SSL tunnel for network daemons (shellinabox).
Oct 13 05:46:15 test-shop systemd[1]: Dependency failed for Shell In A Box Daemon (aka WebShell).
Oct 13 05:46:15 test-shop systemd[1]: shellinabox.service: Job shellinabox.service/start failed with result 'dependency'.
Oct 13 05:46:15 test-shop systemd[1]: stunnel4@webmin.service: Control process exited, code=exited, status=226/NAMESPACE
Oct 13 05:46:15 test-shop systemd[1]: stunnel4@webmin.service: Failed with result 'exit-code'.
Oct 13 05:46:15 test-shop systemd[1]: Failed to start Universal SSL tunnel for network daemons (webmin).
Replies (3)
You're most welcome, thanks for confirming
Reply 1Thanks (it works).
Reply 2Thanks for the quick response. Your suggestion worked, and saved me a lot of time and worry. Much appreciated.
Unfortunately v16.x won't run privileged unless "nested"
Reply 3Unfortunately v16.x won't run privileged unless "nested" (it's an issue with Debian Buster and systemd within limited namespaces).
Regardless, I highly doubt that's your issue. It may be related to a permissions issue, but it shouldn't matter whether the host is privileged or unprivileged. If it's permissions related, it's probably more likely to be because the webserver user (www-data) can't write to a sub-directory of /var/www.
For what it's worth, a 500 error essentially means a server error. Ideally the Apache logs (in /var/log/apache2) should give more details, but as I say, I suspect that permissions may be related.
To rule out permission issues, please ensure that all files are owned by the webserver user:
chown -R www-data:www-data /var/www/prestashop
You're most welcome and thanks for posting back to confirm.
I've opened an issue on our tracker so we can tweak the permissions for next release. Although as I noted in the issue, regarding your theme issue, if you unpacked the zip file as root, then that may be an unrelated issue (IIRC we include the "one-click upgrade" though).