• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Magento 2 situation

custer

Administrator
Staff member
Hi everyone,

Recently there's been a huge influx of posts about Magento 2 installation issues. We too are unhappy that Magento 2 installation experience hasn't been smooth in Plesk so far and we'd like to change this.

Historically there's been only one "official" way to install web applications in Plesk -- and that was APS (Application Packaging Standard). APS was initially developed to install and update your typical web app in a shared hosting environment. The thing is, Magento 2 is not a "typical web app", and it isn't really suited for shared hosting environment -- you gotta have the whole server (or VPS) dedicated to your Magento 2 instance if you want to do anything even remotely serious with it.

Unfortunately, it's not really feasible to fix all Magento 2 installation issues using the APS technology. That's why we are now planning to deliver Magento 2 via the Magento Toolkit extension in the future. It will function similar to WordPress Toolkit extension, and its initial focus will be the proper installation and functioning of Magento 2 on Plesk servers. We hope this will make the Magento 2 experience much smoother in Plesk.

Let us know if you have any questions or comments!
 
Very interesting.. I hope this does not mean you are going to limit installations to 1 per server? Magento 2 has been working just fine here in a mix of imported / installed by hand / installed by APS without issue.

It works just fine in a shared hosting environment (provided the server is suitably powerful)
 
Last edited:
I am happy to hear that. Is there any ETA for this extension, even beta ?

@Dx3webs When you installing by hand did you make nay modification to installed files?
My only problems occurs, when I try to update M2 through CLI or from M2.
 
Very interesting.. I hope this does not mean you are going to limit installations to 1 per server? Magento 2 has been working just fine here in a mix of imported / installed by hand / installed by APS without issue.

It works just fine in a shared hosting environment (provided the server is suitably powerful)

We are definitely not going to limit Magento installations to 1 per server. Even if you want a single Magento instance on a dedicated server, chances are you will want a second instance for staging and testing purposes.
 
I am happy to hear that. Is there any ETA for this extension, even beta ?

@Dx3webs When you installing by hand did you make nay modification to installed files?
My only problems occurs, when I try to update M2 through CLI or from M2.

We are in the research phase right now, so there's no ETA yet. I will keep you guys updated in this thread. :)
 
Using the steps outlined throughout this thread, has anyone gotten their Magento 2 installation working with Plesk?
I understand that users are waiting for the release of the new extension, but I'm trying to solve the my installation problems now. I'm just wondering where everyone left off.

Vultr
OS: Ubuntu 16.04 x64
Magento 2.1.0
Plesk 17.0.17
 
Using the steps outlined throughout this thread, has anyone gotten their Magento 2 installation working with Plesk?
I understand that users are waiting for the release of the new extension, but I'm trying to solve the my installation problems now. I'm just wondering where everyone left off.

Vultr
OS: Ubuntu 16.04 x64
Magento 2.1.0
Plesk 17.0.17
With APS installer it is possible to install magneto 2 successfully.
 
OS: Debian 8 (64 bit)
Magento 2.1.0 / 2.0.7
Plesk: 17.0.17 Update #12
Unable to install any magento no matter what.. completely frustrated by fact Plesk have no clue about it. :confused:
Code:
Error: The following error has occurred during the installation of application:
Installation of magento at https://stage.x.com/ failed. Non-zero exit status returned by script. Output stream: 'PHP Fatal error:  Uncaught InvalidArgumentException: Parameter validation failed in /var/www/vhosts/stage.x.com/httpdocs/setup/src/Magento/Setup/Console/Command/InstallCommand.php:150
Stack trace:
#0 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Command/Command.php(236): Magento\Setup\Console\Command\InstallCommand->initialize(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#1 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(874): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(195): Symfony\Component\Console\Application->doRunCommand(Object(Magento\Setup\Console\Command\InstallCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfon in /var/www/vhosts/stage.x.com/httpdocs/setup/src/Magento/Setup/Console/Command/InstallCommand.php on line 150
'. Error stream: 'PHP Fatal error:  Uncaught InvalidArgumentException: Parameter validation failed in /var/www/vhosts/stage.x.com/httpdocs/setup/src/Magento/Setup/Console/Command/InstallCommand.php:150
Stack trace:
#0 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Command/Command.php(236): Magento\Setup\Console\Command\InstallCommand->initialize(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#1 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(874): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#2 /var/www/vhosts/stage.x.com/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(195): Symfony\Component\Console\Application->doRunCommand(Object(Magento\Setup\Console\Command\InstallCommand), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfon in /var/www/vhosts/stage.x.com/httpdocs/setup/src/Magento/Setup/Console/Command/InstallCommand.php on line 150
'.
 
OS: Debian 8 (64 bit)
Magento 2.1.0 / 2.0.7
Plesk: 17.0.17 Update #12
Unable to install any magento no matter what.. completely frustrated by fact Plesk have no clue about it. :confused:

To clarify: are you trying to install Magento 2 via APS package?
 
To clarify: are you trying to install Magento 2 via APS package?
Yes, right, I am doing something wrong?
I managed to install manually several times on Plesk 17, but even after latest updates, can't able to get Magento 2 via APS method.
 
Yes, right, I am doing something wrong?
I managed to install manually several times on Plesk 17, but even after latest updates, can't able to get Magento 2 via APS method.
That is the problem, when you install it mannualy, probably it's not registered in plesk, so that's why you can't update it through plesk.
 
That is the problem, when you install it mannualy, probably it's not registered in plesk, so that's why you can't update it through plesk.
Thanks for your response, I have tried installing using APS method but, I encountered error that I posted above several times for all versions, but when I did manual using Magento composer install with Web Setup Wizard manual method. Magento 2.1.3 was installed properly on same server & account.
It is just me or somebody also facing such errors on Plesk 17, if Yes, how do you guys installed Magento 2 using APS method.
Thanks
 
Thanks for your response, I have tried installing using APS method but, I encountered error that I posted above several times for all versions, but when I did manual using Magento composer install with Web Setup Wizard manual method. Magento 2.1.3 was installed properly on same server & account.
It is just me or somebody also facing such errors on Plesk 17, if Yes, how do you guys installed Magento 2 using APS method.
Thanks
I have standart Centos 7 + Plesk onyx installation. I only changed mariadb repo, so the plesk is installed with mariadb 10.
Everything else is AS IS and works without any problem.
 
Hello everyone, I'm new about Plesk platform. I did not know about Plesk until today because I'm upgrading my server in order to find the best solution for Magento 2 sites.

So my hosting provider suggested me a VPS with Plesk Onyx 17 (2 core 4gb ram 150 ssd unlimited bandwidth or 4 core 8gb ram and 250gb ssd).

I've done a fast test with plesk demo platform. I searched all topics about integration with Plesk and Magento 2 but now I'm lots confused.

I need to migrate all my clients sites in Vps with plesk and I wish you can give me an hand to understand the actual situation about plesk and Magento 2 compatibility also in order to help other users with my equal doubts.

I've read this topic but I prefer to ask all my questions toghether.


1) Varnish caching - Plesk does not official support Varnish, is it true? Is there anyone that managed to use Nginx + Varnish?

2) Redit caching - Is a solution that perform a lots Magento 2 performance. Is it compatibile with plesk? Anyone uses it?

3) Ssh with Git and Composer - Can I have with plesk the possibility to use ssh with Git and Composer without problem?

4) Cronjob with Magento 2 works well? Anyone that uses Magento 2 with plesk can answer? I've found some posts where some webmasters compains about problem with indexer cron job with Magento > 2.x

5) What os is better for plesk? Debain 8 or CentOs 7?

6) Is it possible to use different version of php for each application/site? What's the minium php version supported? Is it possible to use php 5.4 in one or more apps?

7 - Most important issue) During test on plesk admin demo panel I've tried to perform a new installation of Magento 2.

Error: "The app requires the mysql database server version 5.6 or later."

But I previously selected the true php version:

401bbfc3886545a4aaec3722496848b2.png

0ff6bc48d583453484b66a82093fb8ec.png

895dc0b04533426fa34762a44b8fd679.png


What I need to do in order to set php 5.6 to my entire server/plesk platform?

So dear plesk's users did you advise me to use plesk with Magento 2 or there are lots of problems with it?
Is it preferable a Cloud Hosting with all Magento 2 requirements pre-installed?

Thanks at all
 
Hi @nick_ingenia , welcome :)

About your question:
2. You mean "redis", isn't it?
3. You have got a VPS, you don't use a chrooted env, so I don't expect serious troubles with ssh, git and composer in Plesk.
6. Yes.
7. It is about MySQL, not PHP :) You have to install MySQL 5.6+ on the server.
 
Last edited by a moderator:
Thanks Ruslan for your reply.

1) About Varnish cache, have anyone tried to use it?
2) Yes I mean Redis and not Redit. It is compatible with plesk?
4) Cronjob with Magento 2 works well? Anyone that uses Magento 2 with plesk can answer? I've found some posts where some webmasters compains about problem with indexer cron job with Magento > 2.x
5) What os is better for plesk? Debain 8 or CentOs 7?

Thanks
 
Im try to install Magento :

L'installation de magento sous https://xx/ a échoué. Non-zero exit status returned by script. Output stream: 'PHP Fatal error: Uncaught exception 'InvalidArgumentException' with message 'There are no commands defined in the "setup" namespace.' in /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php:501
Stack trace:
#0 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(535): Symfony\Component\Console\Application->findNamespace('setup')
#1 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(192): Symfony\Component\Console\Application->find('setup:install')
#2 /var/www/vhosts/xx/httpdocs/vendor/magento/framework/Console/Cli.php(96): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(126): Magento\Framework\Console\Cli->doRun(Object(Symfony\Component\Console\I in /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php on line 501
'. Error stream: 'PHP Fatal error: Uncaught exception 'InvalidArgumentException' with message 'There are no commands defined in the "setup" namespace.' in /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php:501
Stack trace:
#0 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(535): Symfony\Component\Console\Application->findNamespace('setup')
#1 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(192): Symfony\Component\Console\Application->find('setup:install')
#2 /var/www/vhosts/xx/httpdocs/vendor/magento/framework/Console/Cli.php(96): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#3 /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php(126): Magento\Framework\Console\Cli->doRun(Object(Symfony\Component\Console\I in /var/www/vhosts/xx/httpdocs/vendor/symfony/console/Symfony/Component/Console/Application.php on line 501

Plesk Onyx v17.0.17_build1700161028.14 os_CentOS 7
MariaDB 10.1
CentOS Linux 7.3.1611 (Core)
 
Back
Top