• 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.

Plesk Multi Server preview

Status
Not open for further replies.

custer

Administrator
Staff member
Hi everyone.

As many of you know, we are introducing Plesk Multi Server with Plesk Onyx release. This thread collects the most important information about Plesk Multi Server and explains how to install and try the Plesk Multi Server preview.

What is Plesk Multi Server?

Plesk Multi Server is an extension that allows you to manage multiple Plesk servers from a single Plesk instance.

When will it be released?

We're planning to release it very soon after Plesk Onyx RTM release (which will be in October).

How can I install it?

Installation instructions are available here: https://docs.plesk.com/en-US/17.0/multi-server-guide/about-plesk-multi-server.77093/

What are the limitations of Plesk Multi Server?

Here's the list of current limitations of Plesk Multi Server:
  1. It will only support Plesk Onyx and future Plesk versions
  2. Currently all Plesk servers connected to Multi Server should have the same configuration:
    • Same version of Plesk should be used
    • Same components and capabilities should be available
    • All nodes should be installed on the same OS. This includes both management and service nodes.
  3. The following OSes are supported at the moment:
    • CentOS 7
    • Ubuntu 14.04
    • Ubuntu 16.04
    • Debian 8
  4. Every server should have a valid Plesk installation before it can be used as a management or service node.
  5. Management node cannot be used for hosting - it can only be used for centralized account management.
  6. Currently there is no way to assimilate existing Plesk instances with production data.
  7. Resellers are not yet supported.
  8. Centralized mail with dedicated mail node is not yet supported.
Note: We're looking forward to removing some of these limitations in the future Plesk Multi Server releases.

How Plesk Multi Server will be licensed?
  • Plesk instances serving as management and service nodes should have either Web Pro (30 domains) or Web Host (unlimited domains) licenses. Web Admin (10 domains) licenses are not supported.
  • Multi-server capabilities are unlocked via separate additional license keys for the Plesk Multi Server extension.
    • Note: no any additional license keys are required in case of Preview builds.

Let us know what you think about Plesk Multi Server - all questions, comments and suggestions are welcome!
 
When trying to add a service node:

Node is not synced to the Management node. Error in cURL request: Failed connect to extore.pp.plesk.ru:80; Connection refused

Seems to be a problem at your side.

Looks promising, can't wait for future updates!
 
@Reboot, just checked twice on external server all works properly.
Could you share an access to your server? Or at least provide a full version of Plesk Multi Server extension? (Left Menu>Extensions).
 
The issue has been solved, however, the same error pops up while installing the "DNS slave management extension" under Provisioning Tasks.

[2016-09-15T13:38:46+02:00] DEBUG Begin init procedure
[2016-09-15T13:38:46+02:00] DEBUG Init procedure finished
[2016-09-15T13:38:52+02:00] DEBUG Task has no prerequisite task
[2016-09-15T13:38:52+02:00] DEBUG Run
[2016-09-15T13:38:52+02:00] DEBUG Install DNS slave management extension on all Plesk Multi Server active nodes
[2016-09-15T13:38:52+02:00] DEBUG Install extension on node *snip*...
[2016-09-15T13:38:52+02:00] ERR Error in cURL request: Failed connect to extore.pp.plesk.ru:80; Connection refused
 
@Reboot, this preview doesn't work well with extensions. Extensions support by Multi Server is in active development.
 
All nodes should be installed on the same OS. This includes both management and service nodes.
Ugh, my hopes are dashed yet again :( "Multi-server" as long as they are all Plesk Linux servers. What about us mixed Windows and Linux hosters?
 
Congratulations to the team of Plesk for this excellent work!!!
This functionality we are waiting for a long time, and the other two are the centralizaded DNS nodes (its perfect) and especially centralized mail.

Thanks Team!
 
@malfunction, Windows is not supported now, it's correct. More details, including preliminary plans you can find here https://docs.plesk.com/en-US/17.0/multi-server-guide/about-plesk-multi-server.77093/
That's a 404 :/ We're just trying to plan hardware purchases, network design, migrations of live Plesk Windows and Linux users etc and that's pretty much impossible when we have little idea of what the new system can do or when it will be available. We've tried, and failed, for ten years with Plesk Expand and PPA to get a small distributed network built and we're excited to learn what the new system can do.

Edit: OK, you edited the link, it works now and I see the features. For us we need more than "tentative" to plan a migration to this system though, at least some sort of timeline for Windows and centralized mail (across all platforms), as these things have to be built in to our system from the start.
 
Last edited:
So when I click the "Nodes" tab on the left navigation pane then click on the "Manage node" button for one of the service nodes I get the following error.
ERROR: 500 pm_Exception: The Management Node context is not specified

Any suggestions?
 
Today we have published an updated version of Plesk Multi Server extension.

New features:
  • [Global Tools & Settings] Synchronization of PHP Settings
  • [Global Tools & Settings] Active Plesk Sessions
Bugfixes are too numerous to mention, but the most relevant are:
  • [Fixed] Centralized DNS settings are not available
  • [Fixed] Admin is not able to manage DNS template
  • [Fixed] Task for additional admin provision failed with "ERR trim() expects parameter 1 to be string, array given"
  • ...and more
We're looking forward to your feedback.
 
Hi,

About this feature "Update #3: (Tentative) Centralized mail service on the dedicated node." that propose, I describe some difficulties when centralized solution, are importante points for better control:
- Possible to customize the e-mail storage path, like example storage is an iSCSI-based storage where point of mount is /data or any name;
- In this form of mount is possible add 02 server for dovecot (imap, pop) in high availability with MariaDB in Cluster as example something http://oxpedia.org/wiki/index.php?title=OX_HE_Tutorial_100K;
- Other solution sample, add relay servers for postfix.

Regards
 
Hi,

About this feature "Update #3: (Tentative) Centralized mail service on the dedicated node." that propose, I describe some difficulties when centralized solution, are importante points for better control:
- Possible to customize the e-mail storage path, like example storage is an iSCSI-based storage where point of mount is /data or any name;
- In this form of mount is possible add 02 server for dovecot (imap, pop) in high availability with MariaDB in Cluster as example something http://oxpedia.org/wiki/index.php?title=OX_HE_Tutorial_100K;
- Other solution sample, add relay servers for postfix.

Regards

+1.
 
What about support for CentOS7 with Cloudlinux installed?
Does it work with Plesk Multiserver?
 
What about support for CentOS7 with Cloudlinux installed?
Does it work with Plesk Multiserver?

Pretty much everything that works under CentOS 7 will work with CloudLinux. The real question is: does Plesk utilise the added functionality of CloudLinux?

Remember, a node is just a full Plesk installation that synchronises content with the master node.
 
Pretty much everything that works under CentOS 7 will work with CloudLinux. The real question is: does Plesk utilise the added functionality of CloudLinux?

Remember, a node is just a full Plesk installation that synchronises content with the master node.

It's likely yes, but we can't guarantee this since we don't perform testing of such case.
We are going to support CentOS 7, Ubuntu 14.04/16.04, Debian 8.
https://docs.plesk.com/en-US/17.0/multi-server-guide/installing-plesk-multi-server.77106/
 
Surely CloudLinux would be semi-essential for a stable web hosting node, wouldn't it? Or is it expected that the new Resource Management features in Plesk replace the CloudLinux features entirely?
 
Status
Not open for further replies.
Back
Top