64x64.png?1.2
Plesk Multi Server

Version
1.2.0-494
Revision
bf77e4b
Build
2017-05-19 14:09:34
Author
Plesk
Homepage
http://plesk.com
Documentation
https://docs.plesk.com/en-US/onyx/multi-server-guide/
Platform
Linux
Plesk Version
17.0.17 and up
Category
Server Tools

Description

Plesk Multi Server extension allows managing multiple Plesk servers from a single place, as one would manage just the one Plesk server. All the customer accounts and subscriptions on all connected servers are created and managed in one centralized user interface. ### Features - Centralized customer account management - Centralized subscription management - Subscription load balancing - Global server settings - Out of the box integration with WHMCS (https://marketplace.whmcs.com/product/2606) - Automation by means of XML API or CLI ### Licensing Plesk Multi Server is a paid extension, each node requires two licenses be installed. It requires one **Plesk Product License Key** ("Web Pro" or "Web Host") and one **Plesk Multi Server Extension License Key** ($10 or €9 per month) be purchased and installed per node. ### More Information For more details on Plesk Multi Server, see the following [Plesk Multi Server Guide](https://docs.plesk.com/en-US/17.0/multi-server-guide/about-plesk-multi-server.77093/)

Changes

# 1.2.0 (19 May 2017) * [+] A Plesk server having active subscriptions can now be added to a Plesk Multi Server infrastructure as a new service node. * [+] A Plesk server having active subscriptions and being a service node in a Plesk Multi Server infrastructure can now be removed from it and turned into a separate Plesk server. * [-] A service node could not be added if mail service was not installed on the management node. (EXTPMS-1333) * [-] A service node could not be added if DNS server was not installed on the management node. (EXTPMS-1334) * [-] Under certain circumstances, an error occurred on the Plesk Multi Server Settings page, making it unavailable. (EXTPMS-1315) * [-] A task 'Sync DNS records with DNS template', running for a long time, could fail by timeout, returning HTTP response code 504. (EXTPMS-1162) * [-] Earlier, the back synchronization process created a separate task to fetch statistics for each subscription, which caused an additional load on the server and slowed the process. (EXTPMS-1343) Now, by default, statistics for all subscriptions are fetched in a single task, which is run once a day. This behaviour can be configured in `panel.ini`: [ext-plesk-multi-server] statistics.period = 'backsync' # 1.1.3 (23 March 2017) * [*] Compatibility fixes with Plesk Onyx 17.5. * [-] During upgrade of the Plesk Multi Server extension, service node synchronization was performed thus changing service nodes status to "Being activated" and making them unavailable for management. (EXTPMS-1293) * [-] An administrator could not create a new subscription on a service node if a public IP address was assigned to the default shared IP address. (EXTPMS-1184) # 1.1.2 (20 March 2017) * [+] Multiple performance improvements related to task management were made. * [-] A confusing error message appeared in the Plesk Multi Server user interface during operations with prohibited domain names. (EXTPMS-1274) * [-] During synchronizing a subscription with its service plan, the "Permanent SEO-safe 301 redirect from HTTP to HTTPS" option became disabled in the subscription's hosting settings, though, in the service plan's settings, this option was enabled. (EXTPMS-1239) * [-] The "Tasks" page loaded too slowly during operations with tasks in case of many tasks. (EXTPMS-1240) * [-] After renaming a subscription, its name was not changed in the list of subscriptions on the management node. (EXTPMS-1214) * [-] If a task on a service node failed by timeout, the service node was always set to the "Unavailable" status. (EXTPMS-1235) * [-] A service node became unavailable in the case of a web server configuration error. (EXTPMS-1212) * [-] When a service node was disabled and then enabled, DNS zone template synchronization started while the DNS zone templates of the service node and the management node were already in sync. (EXTPMS-1217) * [-] When clicking the "Manage Node" link in the management node user interface, the HTTP connection was changed to HTTPS in the service node's URL. (EXTPMS-1164) * [-] If there were non-critical issues during service nodes synchronization, the administrator was not notified about them. (EXTPMS-1110) * [-] The administrator could not search for tasks with the "New" and "Queued" statuses in the tasks list. (EXTPMS-1121) * [-] The administrator could not sort tasks in the tasks list by the "Action" field. (EXTPMS-1109)

Screenshots

Reviews