Issue Migrator ...

[La Linea]

Hi everyone!

When trying to start a migration from a freshly installed Centos 7.4 Server with Onyx 17.5.3 I always get the error:

Failed to connect to target Plesk Server by Plesk API: <urlopen error [Errno 110] Connection timed out>​

The debug.log states:

+|2018-02-08_15:53:03,336|D|MT|hosting_check.utils.http_client|||Unable to import NSS. We will use OpenSSL
+|2018-02-08_15:53:03,380|I|MT|core.migrator|||Initialize Plesk Migrator
+|2018-02-08_15:53:03,381|D|MT|core.utils.panel_detector.source|||Source panel (specified in configuration file): plesk
+|2018-02-08_15:53:03,382|D|MT|core.runners.base|||Execute command on the local server: plesk db "SELECT name FROM Modules WHERE name = 'plesk-multi-server'"
+|2018-02-08_15:53:03,419|D|MT|core.runners.base|||Command execution results:
=|2018-02-08_15:53:03,419|D|MT|core.runners.base|||stdout:
=|2018-02-08_15:53:03,419|D|MT|core.runners.base|||stderr:
=|2018-02-08_15:53:03,419|D|MT|core.runners.base|||exit code: 0
+|2018-02-08_15:53:03,420|D|MT|core.utils.panel_detector.target|||Target panel (automatically detected): plesk
+|2018-02-08_15:53:03,452|I|MT|plesk.connections.target_connections|||Target Plesk host: 172.31.1.100
+|2018-02-08_15:53:03,455|I|MT|plesk.source.plesk.connections.source_connections|||Source Plesk 'source' host: <correct_public_ip>
+|2018-02-08_15:53:03,456|I|MT|plesk.connections.target_connections|||Target Plesk host: 172.31.1.100​

In Tools & Settings > IP Addresses > "172.31.1.100" the public IP address is configured (and Reread IP has already been tried as well).

SSH from and to either mashine works flawlessly, however, the migrator doesn't even attempt to connect the source (not a single network packet) while the "preparing migration" message is being displayed ... ?!?

The last time I had to migrate a box (either with some early 17.x versions or one of the good old 12.x versions) there have not been any such problems within the same NAT network.

System Infos:

Component name - Component version
bind - 9.9.4-51.el7_4.2
dovecot - 2.2.27-centos7.17031716
dovecot-pigeonhole - 0.4.16-centos7.17031614
fail2ban - 0.9.6-centos7.17031414
httpd - 2.4.6-67.el7.centos.6
modsecurity - 2.9.0-centos7.17031417
mysql - 5.5.56-2.el7
php - 5.4.16-43.el7_4
php-fpm - 5.4.16-43.el7_4
php56 - 5.6.33-centos7.18010913
php70 - 7.0.27-centos7.18010912
php71 - 7.1.14-centos7.18020212
php72 - 7.2.2-centos7.18020212
phpmyadmin - 4.6.6-cos7.build1705170314.17
phppgadmin - 5.1-cos7.build1705170314.17
postfix - 2.10.1-6.el7
psa - 17.5.3-cos7.build1705170317.16
psa-api-rpc - 17.5.3-cos7.build1705170317.16
psa-autoinstaller - 3.21.0-centos7.17031018
psa-backup-manager - 17.5.3-cos7.build1705170317.16
psa-horde - 5.2.13-cos7.build1705170314.17
psa-imp - 6.2.17-cos7.build1705170314.17
psa-logrotate - 3.8.2-cos7.build1705170314.17
psa-mod-fcgid-configurator - 2.3.9.5-centos7.17031522
psa-proftpd - 1.3.5d-cos7.build1705170314.14
psa-spamassassin - 17.5.3-cos7.build1705170317.16
psa-turba - 4.2.18-cos7.build1705170314.17
roundcube - 1.2.7-cos7.build1705171115.16
spamassassin - 3.4.0-2.el7

Any ideas?

regards,
-ll

 

[Bitpalast]

172.31.1.100 cannot be accessed by SSH. Check all of your firewalls, it is most likely a firewall issue. If your provider has an extra firewall before the server, disable that one, too.

 

[La Linea]

172.31.1.100 cannot be accessed by SSH. Check all of your firewalls, it is most likely a firewall issue. If your provider has an extra firewall before the server, disable that one, too.

Thank you very much for your reply, but no, this isn't a firewall problem. As I have said SSH works perfectly from either side.

The problem is obviously this:

+|2018-02-08_15:53:03,452|I|MT|plesk.connections.target_connections|||Target Plesk host: 172.31.1.100​

"Target Plesk" is either localhost or the public IP. Isn't that the only thing the assignment of the public IP is done for?

 

[Bitpalast]

172.31.1.100 cannot be accessed by SSH from the outside. Test it with a client like PuTTY. How was your test done that you came to the conclusion that SSH connections work?

 

[AYamshanov]

Hi La Linea,

Could you check connectivity from the target host (172.31.1.100) to itself by telnet on 8443 port?
telnet 172.31.1.100 8443

 

[La Linea]

Sorry, you don't access the server through the private IP. You have to use the public IP or connect to localhost.

For further information see: VServer/en – Hetzner DokuWiki

"With the CX models the IPv4 address of the virtual server is a private IP, which is configured 1:1 via NAT on the public IP. Currently the private IP is the same for all: 172.31.1.100. The public IP is displayed in the Robot."​