Hy together, I have migrated suceccfully some data from my old server to my new server (ubuntu 18.04 3.2.9.p1 to ubuntu 22.04 with actual ispconfig) with the ISPCONFG migration tool. I have migrated all clients, ftp, mysql an web data. At the end of the migration I get the following errors: Code: 2024-04-02 13:05:38 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:38 - [INFO] Trying again (server_config_set) 2024-04-02 13:05:40 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:40 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:40 - [INFO] Trying again (server_config_set) 2024-04-02 13:05:42 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:42 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:42 - [ERROR] API call to server_config_set failed. 2024-04-02 13:05:42 - [ERROR] JSON API ERROR. Arguments sent were: array ( 'server_id' => '1', 'section' => 'web', 'key' => 'check_apache_config', 'value' => 'y', 'session_id' => 'd9aff97620c7ebd4856ad73cf385e05d8173d017e', ) 2024-04-02 13:05:42 - [WARN] Failed setting apache config check active on the target web server. 2024-04-02 13:05:42 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:42 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:42 - [INFO] Trying again (server_config_set) 2024-04-02 13:05:44 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:44 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:44 - [INFO] Trying again (server_config_set) 2024-04-02 13:05:46 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:46 - [ERROR] JSON API ERROR in API call (server_config_set): NO ACCESS 2024-04-02 13:05:46 - [ERROR] API call to server_config_set failed. 2024-04-02 13:05:46 - [ERROR] JSON API ERROR. Arguments sent were: array ( 'server_id' => '1', 'section' => 'server', 'key' => 'migration_mode', 'value' => 'n', 'session_id' => 'd9aff97620c7ebd4856ad73cf385e05d8173d017e', ) 2024-04-02 13:05:46 - [WARN] Failed setting migration mode inactive on the target web server. 2024-04-02 13:05:46 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:46 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:46 - [INFO] Trying again (system_config_set) 2024-04-02 13:05:48 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:48 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:48 - [INFO] Trying again (system_config_set) 2024-04-02 13:05:50 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:50 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:50 - [ERROR] API call to system_config_set failed. 2024-04-02 13:05:50 - [ERROR] API call to system_config_set failed. o server_config_set failed. 2024-04-02 13:05:46 - [ERROR] JSON API ERROR. Arguments sent were: array ( 'server_id' => '1', 'section' => 'server', 'key' => 'migration_mode', 'value' => 'n', 'session_id' => 'd9aff97620c7ebd4856ad73cf385e05d8173d017e', ) 2024-04-02 13:05:46 - [WARN] Failed setting migration mode inactive on the target web server. 2024-04-02 13:05:46 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:46 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:46 - [INFO] Trying again (system_config_set) 2024-04-02 13:05:48 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:48 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:48 - [INFO] Trying again (system_config_set) 2024-04-02 13:05:50 - [WARN] Curl exception: cURL error: [7] Failed to connect to web.bandalo-it.de port 8080: Connection refused 2024-04-02 13:05:50 - [ERROR] JSON API ERROR in API call (system_config_set): NO ACCESS 2024-04-02 13:05:50 - [ERROR] API call to system_config_set failed. 2024-04-02 13:05:50 - [ERROR] JSON API ERROR. Arguments sent were: array ( 'section' => 'sites', 'key' => 'dbname_prefix', 'value' => 'c[CLIENTID]', 'session_id' => 'd9aff97620c7ebd4856ad73cf385e05d8173d017e', ) 2024-04-02 13:05:50 - [WARN] Failed restoring prefixes on target. You find them under system -> Main config -> Sites. So now all datas are migrated, but the apache is deactivated on the target server and some other thins (see log). So why I get these errors ? And how can I manually correct it ? I don´t know where to do it manually on the target server. Thank you fpr your help.
Apache could not start with the migrated configuration and therefore the Migration Tool was unable to communicate with the new server as the API endpoint was down. This does not mean that the migration failed, the tool was just not able to switch off migration mode and to restore database and FTP and shell user prefixes at the end of the migration. Check Apache error.log file and also the errors that were shown when you try to start Apache. This can, e.g., happen when your old Apache config uses Apache modules that are not installed on the new system or when you use a different LE client on the source and target system.
This is what I have found in the apache log Code: Tue Apr 02 12:45:10.281871 2024] [ssl:warn] [pid 1715:tid 140162365163392] AH01906: webserveradress:8080:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Tue Apr 02 12:45:10.281964 2024] [ssl:error] [pid 1715:tid 140162365163392] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=webserveradress,OU=IT,O=None,L=None,ST=None,C=DE / issuer: CN=webserveradress,OU=IT,O=None,L=None,ST=None,C=DE / serial: 5EB9E344D74CE71159617909> [Tue Apr 02 12:45:10.281969 2024] [ssl:error] [pid 1715:tid 140162365163392] AH02604: Unable to configure certificate webserveradress:8080:0 for stapling [Tue Apr 02 12:45:10.283169 2024] [ssl:warn] [pid 1715:tid 140162365163392] AH01906: webserveradress:8081:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?) [Tue Apr 02 12:45:10.283244 2024] [ssl:error] [pid 1715:tid 140162365163392] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=webserveradress,OU=IT,O=None,L=None,ST=None,C=DE / issuer: CN=webserveradress,OU=IT,O=None,L=None,ST=None,C=DE / serial: 5EB9E344D74CE71159617909> [Tue Apr 02 12:45:10.283249 2024] [ssl:error] [pid 1715:tid 140162365163392] AH02604: Unable to configure certificate webserveradress:8081:0 for stapling [ N 2024-04-02 12:45:10.3081 17851/T1 age/Wat/WatchdogMain.cpp:1373 ]: Starting Passenger watchdog... [ N 2024-04-02 12:45:10.3220 17854/T1 age/Cor/CoreMain.cpp:1340 ]: Starting Passenger core... [ N 2024-04-02 12:45:10.3221 17854/T1 age/Cor/CoreMain.cpp:256 ]: Passenger core running in multi-application mode. [ N 2024-04-02 12:45:10.4088 17854/T1 age/Cor/CoreMain.cpp:1015 ]: Passenger core online, PID 17854 [Tue Apr 02 12:45:10.410119 2024] [:error] [pid 1715:tid 140162365163392] python_init: Python version mismatch, expected '3.10.2', found '3.10.12'. [Tue Apr 02 12:45:10.410149 2024] [:error] [pid 1715:tid 140162365163392] python_init: Python executable found '(null)'. [Tue Apr 02 12:45:10.410162 2024] [:error] [pid 1715:tid 140162365163392] python_init: Python path being used '(null)'. [Tue Apr 02 12:45:10.410190 2024] [:notice] [pid 1715:tid 140162365163392] mod_python: Creating 8 session mutexes based on 2 max processes and 25 max threads. [Tue Apr 02 12:45:10.410218 2024] [:notice] [pid 1715:tid 140162365163392] mod_python: using mutex_directory /tmp [Tue Apr 02 12:45:10.432336 2024] [mpm_event:notice] [pid 1715:tid 140162365163392] AH00489: Apache/2.4.52 (Ubuntu) mod_fcgid/2.3.9 OpenSSL/3.0.2 Phusion_Passenger/6.0.10 mod_python/3.5.0+git20211031 Python/3.10.12 configured -- resuming normal operations [Tue Apr 02 12:45:10.432357 2024] [core:notice] [pid 1715:tid 140162365163392] AH00094: Command line: '/usr/sbin/apache2' [Tue Apr 02 12:45:10.432389 2024] [mpm_event:warn] [pid 1715:tid 140162365163392] AH00488: long lost child came home! (pid 16397) [ N 2024-04-02 12:45:10.6686 16410/T1 age/Cor/CoreMain.cpp:1325 ]: Passenger core shutdown finished [ E 2024-04-02 12:45:12.5924 17854/T5 age/Cor/SecurityUpdateChecker.h:521 ]: A security update is available for your version (6.0.10) of Phusion Passenger(R). We strongly recommend upgrading to version 6.0.20. [ E 2024-04-02 12:45:12.5925 17854/T5 age/Cor/SecurityUpdateChecker.h:526 ]: Additional security update check information: - [Fixed in 6.0.14] [CVE-2018-25032] zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches. - [Fixed in 6.0.14] A use after free memory safety issue was introduced in 6.0.12, and fixed in 6.0.14. - [Fixed in 6.0.19] [CVE-2023-38545] A vulnerability existed in libcurl before 8.4.0 which was the library used for Passenger proxy functionality. Exploiting this vulnerability would require two preconditions. First a SOCKS5 proxy to be configured for Passenger licensing, anonymous telemetry, or security u> [Tue Apr 02 13:49:25.314352 2024] [ssl:emerg] [pid 106679:tid 140584961288064] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/ispconfig/httpd/customerwebside/error.log for more information AH00016: Configuration Failed [Tue Apr 02 13:50:00.290605 2024] [ssl:emerg] [pid 106726:tid 140597755045760] AH02311: Fatal error initialising mod_ssl, exiting. See /var/log/ispconfig/httpd/customerwebside/error.log for more information AH00016: Configuration Failed So I have deleted two vhosts and now the Apache starts. Thank you !
You must disable server migration mode under system > server config, otherwise your system will not create new let's encrypt SSL certs.
