• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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