Important Plesk Migrator extension

[solarweb]

Hi,

We have an error on Plesk Migrator since this morning.

I can see that there was an upgrade to version 2.29.0-3148

When you clic on an already registered migration, to go to detail there is an error page :

500 TypeError​

version_compare(): Argument #1 ($version1) must be of type string, array given

Best regards,

 

[feken]

I'm having the same problem..

 

[feken]

Upgrading the extension fixed it for me..

 

[solarweb]

Hello,

Ok, for now it don't seems I have an upgrade available.

What version do you have ?

 

[JustinWux]

Hello,

Ok, for now it don't seems I have an upgrade available.

What version do you have ?

Hey, you might have to press the check now button manually. It should show that version 2.9.14-3114 is available for download

 

[Sebahat.hadzhi]

This issue is related to a bug identified with ID PMT-5634. It has been fixed in version 2.29-1.

 

[solarweb]

Yes you were right.
I forced refresh and done the upgrade.

Thanks for the quick fix !

 

[Woutuit]

Hi,

Is Debian 13 already supported as source server for the migration wizard tool?

Error:

Failed to deploy Python on source server
Cause: Source server OS 'debian 13 x86_64' on the source server 'directadmin' (x.x.x.x) is not supported
That is a critical error, migration was stopped.

System information:

• Source server
  • Control panel: DirectAdmin 1.695
  • OS: Debian 13 x86_64
• Target server
  • Control panel: Plesk Obsidian 18.0.76 Update #2
  • OS: Ubuntu 24.04.4 LTS
  • Plesk Migration: 2.31.4-8796

 

[Sebahat.hadzhi]

@Woutuit , I have opened an internal task for our team to investigate the reported issue. Plesk supports Debian 13, so in theory, the migration should not fail. I will follow up with more details as soon as possible.

 

[Sebahat.hadzhi]

@Woutuit , the behavior was confirmed as a bug identified with ID PMT-5658. Thank you for bringing our attention to the issue. Our team will introduce a fix in the upcoming Plesk release (18.0.77).

 

[Sebahat.hadzhi]

@Woutuit , just wanted to follow-up on the bug you reported. It has been fixed as of Plesk Migrator 2.32.1 (released yesterday). Thank you for bringing our attention to the issue.