Server IP changed

[gamehost.nl]

I've moved my webserver to a new webserver, with a new IP adress.

Also to control the installation of plesk 8.01 (I was using 7.5.4) I initially did some tests and only transfered a few domains.. Everything seemed to be fine.

Only in order to not change all the dns settings of all my domains, I first switched the IP's of both servers.

But now there are 2 ip's fixed in the IP management control and can't remove both.

But when I try to log in to the IP of the old webserver it's still login into the the new server. So, for some reason, Plesk tries to log in all the time at this new webserver and never to the old one.

Is there a solution for this and can I remove the old IP. (the one the old webserver is using now)???

 

[gamehost.nl]

I received a reply from the support from plesk:

Hello,

I assume that your router forwards all connections to new server rather than to old. If you want to access old server you should configure it in your router, or removing that IP from new server.
I see that the both IPs are main on eth0 interface that's very strange. There should be one main IP on eth0 interface and another as alias.

As workaround you can remove that IP manually, using "ifconfig eth0 del <IP> ". And then remove it from psa db:
# mysql -uadmin -p`cat /etc/psa/.psa.shadow` psa

mysql> delete from IP_Addresses where ip_address='<IP>';

I'd done these steps and I noticed the IP is now removed from the Plesk panel.

Unfortunately, when using the migration manager, whatever IP I fill in,
it's all the time trying to loging to it's own server.

Do I need to change this eth0 config also on the other server?

The problem is, the old server is now running on ip 85.92.128.91
(previous it was 85.92.128.89). The new server is now using 85.92.128.89
(previous it was 85.92.128.91). After IP's are swtiched and using the
migration manager I fill in IP 85.92.128.91. This should be the old
webserver, because when trying to access https://85.92.128.91:8443 I can
come into the old webserver, so the IP changes had been changed ok.

But WHY can the migration manager not find the correct IP anymore????