• 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.

Can't remove an old inactive IP address

ChananZ

New Pleskian
Hello,

My Parallels Plesk Panle 11.0.9 (Windows 2008 r2) would not allow me to remove an old IP address.
I've tried using PP Reconfigurator but encountered a problem:

1. I open PP Reconfigurator and click "Change Server IP Addresses"
2. Under IP addresses I see 2 addresses
3. I check the one that is no longer active
4. I select "Existing Address", however NO existing addresses are displayed.

Is there a way to remove this old inactive address somehow.
I should say that we have 2 domains on that server. Both domains are associated with the active IP address.

The funny thing is that when using PP Reconfigurator we see that the inactive IP is still associated with one of the two domains (this is not true).
In short PP Reconfigurator displays DOMAIN 1 and DOMAIN 2 associated with the active IP; while DOMAIN 1 also associated with the inactive IP.

Problem is that we can't upgrade our panel because the upgrade application considers our server to be associated still with the old inactive IP address and can't find the necessary ports for that old IP.

Any help would be appreciated.
 
Looks like that there is database inconsistency. I suggest you contact Support Team. They will check and fix it directly on your server.
 
Back
Top