Search Engine: Elastic

Article ID: 126442, created on Aug 4, 2015, last review on Aug 4, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5


A Plesk node is registered with IP address, say, There is an IP Pool of "Plesk Hosting" type with IP range from to However, is not within exclusions of the IP Pool.

As a result, the IP address was considered as free and eventually assigned to a Plesk Client or a Plesk Domain as dedicated causing all Plesk domains on the node that used shared IP address to stop resolving and fall offline.


Each IP Pool has a set of hardware nodes and groups configurable under Top > Service Director > IP Manager > IP Pools > IP Pool name > Configuration tab > Hardware nodes. Only those nodes' addresses are automatically added to the IP Pool's exclusions.

If the group of the node in question is assigned to the IP Pool but the node address is still not added to the IP Pool's exclusions, it means that the node was added to the group after the IP Pool was configured.


  1. Switch the subscription that auto-gained the IP address to a shared IP address via its Customer Panel: Top > Account Director > Customer Manager > Customers > The subscription owner > Log in to CP > Select Configuration tab > Click Switch to Shared IP

  2. Re-save the IP Pool to re-check nodes groups membership and re-read IP addresses: Top > Service Director > IP Manager > IP Pools > IP Pool in question > Configuration, press Edit and then, without changing a thing, Update. If after that is not in exclusions, add it there by hand.

Please also note that when a hardware node is removed from OBAS its IP address stays in the corresponding IP Pool exclusions and should be removed manually..

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF