• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Resolved IP pool is empty !

dopeboy

Basic Pleskian
I Have Try It And All Works Perfectly!
But when i try to create a customer i have this problem !
Warning: The subscription cannot be created: IP pool is empty
y9xavCc.png
 
Are there any other subscriptions/hosting plans running on the same system? If you set the IP address usage as dedicated it can serve one and only one plan. What you might want to do is set it to shared with the current default site which will enable you to use the same IP for the new site that you're trying to add.
 
I'm unable to create a new subscription. Error: "Es kann kein Abonnement erstellt werden: Der IP-Pool ist leer." (IP-Pool is empty). The solution for this problem as mentioned in other posts is to change IP-Adresses to shared. I have only one IP Adress and it is still set to shared, but the error still appears.

ippool.png


I'm also unable to set SSL Certificates for a domain. It seems that SNI is broken? It sais, that I should use a dedicated IP-Adress for using SSL. But how should I do that, just with one IP dress and more than 50 Domains secured by Let´s Encrypt SSL...
 
found a solution:

The Apache module did not run properly, checked via: service httpd status
There was a configuration error of Plesk. For a subdomain deleted in Plesk, Plesk tried to continue to read configuration data. For some reason the corresponding * .conf was not deleted. After I have deleted it manually everything is fine :)
 
Back
Top