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

Losing contact with server

C

cartoon

Guest
I have been installing a new server running FreeBSD 5.3 and Plesk 7.5 .
Before trying to upgrade from Plesk 6.0 I let the server run for 14 days with Plesk installed but not any active domains.
I sow used the PMM to move the domains from the old server to the new server and all was OK. After migration I changed the IP adresses with reconfigurator on the new server and changed the IP adresses in necesarry conf files ( rc.conf ) . The server is then running without any high server load for 5 to 15 minutes and after that loses the contact with the network. I can reach the server from connected keyboard and there are I can not find any errors. Plesk is running OK on the server, but the connection to the network is lost. ( cant reach the server with SSH ) . Anyone have an idea what can cause this? Maybee a good idea to try to change the network card? ( The connection on the switch have light and show the server as connected) .
 
Forget to say that the old server ( with Plesk 6.0 ) was still running but I changed the IP adress for the old server with reconfigurator
and changed iPs in rc.conf
and the server name for the old server in resolv.conf

This way the new server with Plesk 7.5 should replace the old server but I wanted to run the old server for a few days after upgrade in case anything happend sow I could change hosting back to that server if anything failed ( as it did) .

Question then is: Could there be any other places the IP adresses also has to be changed? ( The old server was running OK on its new IP adresses) .
 
Back
Top