• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Secondary IP Addresses corrupted when Plesk Windows Server is rebooted

Jim Jankowski

New Pleskian
When I reboot my Plesk server (Windows, GoDaddy VPS) using either the GoDaddy Restart or Plesk Server Restart I have to use the Server-->IP Address Repair and ReRead function to get the the websites on the secondary IP Addresses to come up.

The separate IP Addresses each host one website using SSL.

Currently these sites are development only, however I really need to get this fixed before I can go live.

Any help greatly appreciated.
 
If anyone has ANY input please let me know, even if you are having the same problem. I would really like to know if I am the only person experiencing this issue. Also if you are having the same problem I may be able to help you once I get this resolved.
 
Hello,

We faced similar issue with our plesk 12.0 version. We had to manually disable enable the network card or we had to use readd ip tool. After upgrading the plesk to 12.5, all is ok now. You can surely give try if you have older version of plesk.
 
Back
Top