• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Cannot migrate domains because of error 'Subscription xxxx has no IP addresses on target system'

vanlier

New Pleskian
Server operating system version
Source: CentOS Linux 7.9.2009 (Core), target: CloudLinux 9.6 (Georgy Dobrovolsky)
Plesk version and microupdate number
Source: Plesk Obsidian 18.0.71 Update #2 Web Host Edition, target: Plesk Obsidian 18.0.71 Update #2 Web Host Edition
I'm migrating domains from old to new plesk server using the migrator tool. I have 2 problems:

1) Multiple domains fail to migrate or switch DNS with the following error:
Subscription xxxx has no IP addresses on target system

Debug log shows:

Exception:Traceback (most recent call last): File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/safe.py", line 191, in try_subscription_with_rerun func() File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 526, in <lambda> lambda: action.run(self._context, subscription), File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/actions/hosting_settings/convert/fix_dns_zone_inconsistency.py", line 48, in run self._add_missed_a_records_for_ns_records(subscription, target_plesk_version) File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/actions/hosting_settings/convert/fix_dns_zone_inconsistency.py", line 117, in _add_missed_a_records_for_ns_records raise Exception(Exception: Subscription 'xxxxx' has no IP addresses on target system. DNS records won't be changed

2) Source server has external IP, target server has internal IP with NAT. When running the Switch DNS command, the DNS zone on the source is changed to slave with the internal ipaddress of the new server. I already reinstalled the migration extension. I now manually have to fix every dns zone on the source when migrating
 
I found the reason for error 1:

when we have a domain that is only used for DNS pointing to an external website (so no mail or webhosting) then the migrator can't get the IP used for substition in the migrated dns records. Workaround: set mailservice to 'disabled for incoming mail' instead of disabled. Now the migrator can get the IP from the mail service. Ofcourse this is a bug as such domains should be migratable.
 
2) Source server has external IP, target server has internal IP with NAT. When running the Switch DNS command, the DNS zone on the source is changed to slave with the internal ipaddress of the new server. I already reinstalled the migration extension. I now manually have to fix every dns zone on the source when migrating
Did you configured what the public IP address is to the private IP in the IP Addresses Settings? Refer to Running Plesk Behind a Router with NAT for more details.
 
Back
Top