Restrict Plesk license usage by IP ranges

Introduction

Those partners who want to protect their Plesk licenses from being stolen and used at alien servers could use restrictions by IP. There are two types (levels) of such restrictions available in KA:

1. Restrict by IP range(s). IP range(s) are specified at client level in Key Administrator. Applicable to all Plesk licenses under the client.
2. Restrict by individual IP address (so-called "IP binding"). IP address is specified at license level in Key Administrator. Applicable to an individual license. See more details on this here: https://support.plesk.com/hc/en-us/articles/214529225

You can use either type of restrictions for your licenses (or their combination).

Restricting licenses by IP ranges

This setting is available only in Key Administrator user interface:

1. Open client object in KA
2. Open "IP Ranges" tab

View mode

Edit mode

In "Edit" mode you can:

• Turn on or off cloning for Plesk 10+ lease licenses (see below for details)
• Restrict Plesk key usage by IP ranges (see below for details)

Restricting cloning of Plesk 10+ lease license

If you are a partner who wants to use this option, please contact your Sales Representative.

Restricting Plesk license usage by IP ranges

• Restrict Plesk instances to connect to KA and update licenses only from the specified IP ranges.
• All requests to update license from outside of the IP ranges list will be blocked.
• This is typically useful for hosters, who own ASes (IP ranges) and would like to restrict Plesk running only on their servers.

Restricting master key usage

• Allow creating instance keys by master keys only from the specified IP ranges.
• If IP ranges list is empty, then creation of instance keys by master keys is prohibited.
• For security reasons this setting is always turned on.

Important facts to know

• IP restrictions (IP ranges and IP binding) do not work with IPv6. Key Administrator does not have IPv6 address, therefore no IPv6-to-IPv6 routing is possible.
• If you are a partner and use some load-balancing solution in front of Plesk server that causes use of dynamic public IP address, then:
  • You should either take care of directing the outgoing traffic to ka.plesk.com via a permanent public static IP address.
  • Or should not use IP restrictions in KA.
• If you are a partner and have multiple public IP addresses on your server, and any of these IP addresses may be used as an address for outgoing connections, then:
  • You should either take care of directing the outgoing traffic to ka.plesk.com via a permanent public static IP address.
  • Or should not use IP restrictions in KA.