I'm doing an old server migration with ispconfig migrate tool. https://www.howtoforge.com/tutorial...-confixx-plesk-to-ispconfig-31-single-server/ I'm at the migration stage of the domain mail. I was able to migrate some but I have this error on a couples of domains: Code: [ERROR] API call to mail_user_add failed. See log file for details.so.cc) [ERROR] API call to config_value_replace failed. See log file for details. [ERROR] API call to mail_user_add failed. See log file for details.c) [ERROR] API call to config_value_replace failed. See log file for details. [ERROR] API call to mail_user_add failed. See log file for details. [ERROR] API call to config_value_replace failed. See log file for details. [ERROR] API call to mail_user_add failed. See log file for details. [ERROR] API call to config_value_replace failed. See log file for details. [ERROR] API call to mail_user_add failed. See log file for details. [ERROR] API call to config_value_replace failed. See log file for details. In the log file they are all giving the error with the same reason: Code: 022-02-16 20:58:47 - [ERROR] JSON API REPLY ERROR: Mail domain - domain.com - does not exist as primary. - Arguments sent were: array ... etc The old server is live and receiving email! So I imagine the config is still there. I look in the dbispconfig and the table domain is emplty. Maybe it's related because on the new server it's filled with the domains after migration. anybody has an idea on where I should begin to look? Thanks
Does the e-mail domain exist on the SOURCE server? How is the domain set up on name service? Is this error appearing during dry run or the final run of the migration tool? According to Migration Tool documentation at https://www.ispconfig.org/add-ons/ispconfig-migration-tool/ you can contact Migration Tool Support directly. It says so at the end of that web page.
Email domains are in the table mail_domain. The table domain does not contain the email domains, the domain table is used by the domain limit module only, so it should be empty on most systems as this domain limit module is off by default.
>> Takeman Does the e-mail domain exist on the SOURCE server? >> Yes it's receiving emails on the source server How is the domain set up on name service? >> It's the registrar DNS Is this error appearing during dry run or the final run of the migration tool? >> At Both times. >> Till After vérification. the domain is listed in mail_domain table Thanks for your relpies! I'll contact support.
