• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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