• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

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