• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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