Hello, Tried sending this with https://www.ispconfig.org/get-support/?type=migration - But was BLOCKED ??? Using 3.3 on both servers and with Ubuntu 24.04 running NGINX ISPConfig Install on TARGET is 100% OK with Let's Encrypt working on FQDN Problem with migration: You gave me remote user 'remoter' with password 'password' And I shall connect to 'https://serv.server.com:8080/remote/' Is this correct? (y, n): y [ERROR] API call to login failed. See log file for details. Could not connect to api. Please check if the data you provided is correct. Name of the remote user of TARGET ISPConfig3 system [remoter]: No errors in nginx error.log at any time I've tried it in both Dry and Migrate with same results Tried ./migrate and ./migrate --legacy-tls - No difference Ran: wget https://my.private.ip.address:8080 = ( NOTE: USED FQDN ) wget https://serv.server.com:8080 ( OK CONNECTED ) root@serv:~# wget https://serv.server.com:8080 --2025-04-29 19:27:20-- https://serv.server.com:8080 Resolving serv.server.com (serv.server.com)... 127.0.1.1 Connecting to serv.server.com (serv.server.com)|127.0.1.1|:8080... connected. HTTP request sent, awaiting response... 302 Found Location: /login/ [following] --2025-04-29 19:27:20-- https://serv.server.com:8080login/ Reusing existing connection to serv.server.com:8080. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html.1’ index.html.1 [ <=> ] 7.11K --.-KB/s in 0s 2025-04-29 19:27:20 (499 MB/s) - ‘index.html.1’ saved [7284] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wget https://my.private.ip.address:8080 = wget https://123.45.67.891:8080 ( NOT CONNECTED ) No SSL CERT root@serv:~# wget https://123.45.67.891:8080 --2025-04-29 19:32:35-- https://123.45.67.891:8080/ Connecting to 123.45.67.891:8080... connected. ERROR: certificate common name ‘serv.server.com’ doesn't match requested host name ‘123.45.67.891’. To connect to 123.45.67.891 insecurely, use `--no-check-certificate'. root@serv:~# wget --no-check-certificate 123.45.67.891:8080 --2025-04-29 19:42:06-- http://123.45.67.891:8080/ Connecting to 123.45.67.891:8080... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://123.45.67.891:8080/ [following] --2025-04-29 19:42:06-- https://123.45.67.891:8080/ Connecting to 123.45.67.891:8080... connected. WARNING: certificate common name ‘serv.server.com’ doesn't match requested host name ‘123.45.67.891’. HTTP request sent, awaiting response... 302 Found Location: /login/ [following] --2025-04-29 19:42:06-- https://123.45.67.891:8080/login/ Reusing existing connection to 123.45.67.891:8080. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html.2’ index.html.2 [ <=> ] 7.11K --.-KB/s in 0s 2025-04-29 19:42:06 (1.64 GB/s) - ‘index.html.2’ saved [7284] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Any help would be appreciated Thanks Jim
We do not block, but it might be that CloudFlare blocked you for whatever reason. Do you see the connect attempt in the access.log of the new server? If you test with wget, you must use the right URL, which is: https://serv.server.com:8080/remote/ Connecting without /remote/ must redirect you to the login. You can contact our support also by email to migsupport at ispconfig dot org.
I assume you run this on the source server to try to connect to the target server? According to the output, you configured the target server hostname to point to 127.0.1.1 which means you are pointing the target server hostname to localhost on the source server, therefore no connection can leave the server and connections to the target server can not work. And double check that you run the tool on the old server, not the new one, and that you did not used the same hostname on old and new server as a connection to that hostname would never leave the old server when the hostname is the hostname of the old server.
