• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Error: IP pool is empty

JArnoldussen

Basic Pleskian
Whenever I create a new customer in Plesk 10, I get the following error:

Error: IP pool is empty.

What is causing this? I'm using the standard shared IP on the server. Any ideas?
 
Once I create the account, and get the above error, I take a look at the domain, and it claims that it's trying to use a dedicated IP. During the setup stage I absolutely selected the shared IP. Why is it doing this, and how to I change the IP?
 
I ended up opening a ticket on this, and they found the problem. The problem is caused when you change the main A record IP address in the DNS template. By default, this template has <ip> in that field, and I changed it to the static IP of our server. Changing it back to <ip> fixed the problem for now. The support team promised this would be fixed in the next release.
 
Thanks for the update.
Changing back to <ip> isn't an option here, as that would switch the A record IP to the Private IP of the server.
Hopefully they have a real fix.
 
Back
Top