• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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