To prevent the usage of Plesk licenses on multiple servers (which is against the Plesk End-User License Agreement), the algorithm for identifying such licenses was optimized from November 2020. As a result, from December 2020 onwards, mid-month, Plesk notifies Partners about which licenses from their inventory are used on multiple servers.
Note: If multi-use is established as having continued for more than 30 days, the corresponding license fee will be charged for each server that uses the same license.
The reports delivered to the billing addresses mid-month include a list of all licenses identified for multi-use at the moment when the check was performed.
If the multi-use type corresponding to a license is marked as "confirmed", the situation has been ongoing for more than 30 days and will be correspondingly charged for, as described above.
The licenses used on multiple servers for less than 30 days are marked as "potential" multi-use. They will not be charged, however, they are a warning.
If no report is received, it means no multi-use licenses were detected for the respective account.
Note: If a license is used on multiple servers even for one single day, it already violates the Plesk End-User License Agreement. The 30 days established threshold was set to confirm license multi-use, as well as act as a buffer period to adjust the situation. 30 days is a sufficient time period for Plesk to confirm multi-use, as well as for partners to stop multi-use and/or to forewarn their customers about extra billing. However, mind that Plesk is constantly improving the frequency and accuracy of server reporting. That is why the duration of allowed multi-use, which is 30 days at the moment, can be changed at any time.
Note: Potential multi-use licenses should be checked in Partner Central > Manage Licenses > PLSK.01234567.0000 > Instances tab. Check how many servers are running this license and for how long (check IP address and last date columns). Actions should be taken to the licenses, which run on 2 or more servers simultaneously up to the date the check is done.
If a partner was notified about the usage of licenses on multiple servers, the partner can undertake one of the following actions:
Buy and install a separate license for each server. This is the recommended solution, and most reliable way to prevent potential multi-use from becoming confirmed.
Terminate the license in question. The next server hit will remove the license from the server. This hit will be considered in the multi-use algorithm and multi-use status can still become "confirmed". However, if termination happens before license renewal for the next month, such cases will not be included in the billing report for further processing. So, if you decide to terminate the license in question, it should happen before the license update date. In this case, a partner can avoid billing even for confirmed multi-use in the current month.
Set up auto IP binding, change IP binding behavior to "Lookup and restrict" or, if it is known exactly which server should use the license, bind to a specific IP address, and change IP binding behavior to "Lookup and restrict". Please note, that with the next update date, all servers with this license hit in KA. Requests from servers with a different IP than the bound one fail, but these hits will still be considered in violation of Plesk EULA. So, IP binding won’t help to avoid billing in the current month and likely next month too. However, IP binding helps to stop multi-use for further months. For more details about IP binding please refer to the dedicated article.
Contact end-user and bill for multi-use in advance.
For more details on this topic, partners should contact their assigned Sales representative or use the Contact form on the Plesk website.