Hi Guys, Doing some pre-migration testing and getting the following errors/warnings. Old server = Debian 12 (Updated from 11), ispconfig 3.2,12p1, billing module 2.0.14 rev 43. (With issues) New server = Debian 12, ispconfig 3.2,12p1, billing module 2.0.14 rev 43. Code: [WARN] The target server has a different Let'sEncrypt client than this server. We cannot copy over certificates! Can I get the system to re-generate the certs? (I thought the server was already using ache.sh as it's on the server, but so is the /etc/letsencrypt/ directory. Both have have recent file dates on them.) Code: [1/15] <Website> processing domain.net.au with autosub www Warning: Undefined variable $parent_id in /root/migration/v82/includes/importer.inc.php on line 1191 [2/15] <Website> processing domain2.com.au with autosub www Warning: Undefined variable $parent_id in /root/migration/v82/includes/importer.inc.php on line 1191 The same warning for all domains. Code: [14/14] <MailDomain> processing anotherdomain.com.au Warning: Undefined array key "domain" in /root/migration/v82/migrate.php on line 1869 Code: [1/2] <MailAliasDomain> processing mail aliasdomain @bigcompany.com.au -> @emailbigcompany.com.au Warning: Undefined array key "domain" in /root/migration/v82/migrate.php on line 1869 Code: Warning: Undefined array key "_PARENT_" in /root/migration/v82/includes/importer.inc.php on line 1941 [1/5] <BlackWhiteList> processing whitelist [email protected] Warning: Undefined array key "_PARENT_" in /root/migration/v82/includes/importer.inc.php on line 1950 Code: [ERROR] API call to billing_invoice_company_get failed. See log file for details. Log file: Code: 2024-10-25 11:34:10 - [INFO] Directory /etc/letsencrypt/live does not exist. 2024-10-25 11:34:11 - [INFO] Directory /root/.acme.sh exists. Both of these dirs exist on the server. Code: 2024-10-25 11:34:16 - [ERROR] JSON API ERROR in API call (billing_invoice_company_get): HTTP CODE 500 2024-10-25 11:34:16 - [INFO] Trying again (billing_invoice_company_get) 2024-10-25 11:34:16 - [ERROR] JSON API ERROR in API call (billing_invoice_company_get): HTTP CODE 500 2024-10-25 11:34:16 - [INFO] Trying again (billing_invoice_company_get) 2024-10-25 11:34:17 - [ERROR] JSON API ERROR in API call (billing_invoice_company_get): HTTP CODE 500 2024-10-25 11:34:17 - [ERROR] API call to billing_invoice_company_get failed. 2024-10-25 11:34:17 - [ERROR] JSON API ERROR. Arguments sent were: array ( 'primary_id' => array ( 'company_name' => 'ActIT!', ), 'session_id' => 'aae796dad47f5e7c23a50c9a647fdadc28d430c84', ) 2024-10-25 11:34:17 - [INFO] Skipping billing invoice_settings I have only shorten the company name for this post, it's 11 characters in length and does have the ! on the end. I can send un censored logs etc to the support system is needed/required. Thanks, Stephen
Yes, turn off SSL for the website, press save, turn it on again and press save. Your main problem will be that you can not request new certs before the domains point to the new server. Most of the warnings are likely inconsistencies in your old database. If this causes any issues in a specific case can be seen only after you did the real migration when you can check if the imported results are ok or not. Regarding Billing Module, check in Apache/Nginx error.log why the new server returns a 500 error. If you like to get support for the Migration Tool, please contact us here: https://www.ispconfig.org/get-support/?type=migration This forum is not a support source for the Migration Tool.
HI Till, as in "/var/log/apache2/error.log" ? That only has errors from hours before running the migration (Still in dry mode). Just tried to submit a report to the "get support page" and got a "Sorry, you have been blocked" error from cloudflare...
Please send us the support email directly to support at ispconfig dot org then. Sometimes, Cloudflare is a bit too protective.
Hi Till, Have just sent a email with log file, database from current server, and database from new server after having performed a migration. Stephen
