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

Urgent! - Serious error with plesk admin login page

Smartnet

Basic Pleskian
Dear all,
recently we purchased a new virtual linux hosting account from Godaddy with Plesk 9.3.0 pre installed. From our old virtual server with Plesk 9.3.0 we created a full backup which we restore successfully to the new server by using the restore option thru personal FTP account. Then we've done a plesk update to 9.5.2 successfully also. All these days we were noticing that when we were logging out from the plesk panel in our new server , it wasn't logging out but it was redirecting us to the login page of the old server! - but we thought it had to do with browser's cache - Today a disaster happened. When we tried to login to the new server , we have a time out error which inform us that " The server at ip-xxx-xx-xx-xx.ip.secureserver.net is taking too long to respond. What drives us crazy is that the ip which is mentioned is not the ip of the new server (as it should be ) but it's the ip of the old one!! Godaddy experts told us that it's not their fault and it has to do with plesk!

Please respond asap cause we really worry about that.
 
OK. that's what we discovered. If someone , somehow is going to create an FTP plesk server backup from GUI and then restore this to another server with same version of plesk (9.3.0) , then even while the restore process he will be asked by the system to set the new ip address of the server , even if all hosts will work perfect at the new ip addresses , for some reason plesk's panel login page will pass first from the old server's ip address and then gets redirected to the new one. Then when you decide to deactivate the old server ....you'll not be able to login to the new one. What we've done...we reactivated the old one , and now we're going to make backups of each host , reprovision the server and restore the backup for each host.
We hope we'll be lucky.
 
Back
Top