Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Magento 2 plesk compatibility issue
- Thread starter Ahmad12
- Start date
KonstantinosS
Basic Pleskian
I think Magento 2 requires MySQL 5.6 and Plesk comes with a previous version out of the box. If you can have Plesk handle mail and DNS, you can point an external web and database server, one that has Varnish installed as well, and install it there. In most cases, Magento is not suitable for shared hosting, as it's pretty demanding on CPU and RAM.
bulent
Regular Pleskian
My plesk install is with mariadb 10, so that wasn't the problem. Most of the problems were related to ownership and permissions.
I know that magento uses a lot of resources, but at the moment I have plenty of them.
The strange thing is that I have shared hosting with cpanel and softacolus, and they have magento 2 out of the box.
Hi everyone,
const WRITEABLE_DIRECTORY_MODE = 0755; // was: 0770
const WRITEABLE_FILE_MODE = 0644; // was: 0660
This will make sure that Magento creates files and directories with the correct permissions.
Next, reset the current file permissions by running the following command via SSH (I assume that your current work directory is the root installation dir):
cd ./pub
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
This should reset file permissions to 644 and directory permissions to 755 inside the ./pub directory and all sub-directories.
- We're planning to release a working version of Magento 2 APS package soon.
- Try the following instructions and let us know if they help: http://devdocs.magento.com/guides/v2.0/install-gde/prereq/file-system-perms.html
- If the instructions above do not help, try the following:
const WRITEABLE_DIRECTORY_MODE = 0755; // was: 0770
const WRITEABLE_FILE_MODE = 0644; // was: 0660
This will make sure that Magento creates files and directories with the correct permissions.
Next, reset the current file permissions by running the following command via SSH (I assume that your current work directory is the root installation dir):
cd ./pub
find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
This should reset file permissions to 644 and directory permissions to 755 inside the ./pub directory and all sub-directories.
Also, if you're using Nginx + PHP-FPM, the following advice from Alexander Sibert should help (thanks Alex!):
https://twitter.com/alexandersibert/status/670993228418691073
https://twitter.com/alexandersibert/status/670993228418691073
bulent
Regular Pleskian
Did you gave extra permission in phpmyadmin and how did you make it work(2 or 3 from previous post) ?
Can you explain exact steps?
Ron Abbate
New Pleskian
Hi Custer. Do you have an ETA on when that APS package to be released?
We're testing it right now, so if everything goes smooth, we'll release it by the end of this week (hopefully). If problems are found, realistic ETA would be the end of March.
DB user should have full permission on the DB, I did not understand the rest of your question.
Dx3webs
Basic Pleskian
magento 2 requires these additional permissions for your DB user: http://screencast.com/t/XyXWGxCpIisj
bulent
Regular Pleskian
Yeep, I have found that, but I had different file permission issues, so at the moment waiting for the official package from plesk.
Similar threads
- Locked
