Issue Plesk Migrator - "Can not connect to the Plesk database"

[Jan Bludau]

Server operating system version

Debian 12.5

Plesk version and microupdate number

Version 18.0.61 Update #4

Hello Plesk Community,

I'm faced with a new problem with the Plesk extension "Plesk Migrator" that I'm not familiar with. Within tail -f /var/log/auth.log I can see how the target computer logs into the source computer. So far so good, but the migrator fails to connect correctly to the database.

The following error message appears:

Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Failed to execute SQL query on panel database: Can not connect to the Plesk database. Please, check database server is running.
That is a critical error, migration was stopped.

How can I change the Plesk admin database password so that the migrator can access it?

I tried the following:

plesk bin admin --set-admin-password -passwd 'MyPWD'

The error message remains, however.

 

[Maarten.]

This error looks like you didn't use the root credentials for the source server when starting migration in Plesk Migrator.

 

[Jan Bludau]

I am using the root credentials. I had to use a VPN service to open the ports I needed, but I thought everything goes from server A to server B without my own laptop.

To connect to the database, a source/target server connection seems to have to be established locally to my PC.

bizarre.

 

[Maarten.]

I'm not sure if I understand why you have to use your laptop. A migration goes from server A to B.
Is the SSH option "PermitRootLogin no" active on the source server?

 

[Jan Bludau]

i'm not at home...i'm at a new workset environment..

the "PermitRootLogin" setting is "yes" - sudo nano /etc/ssh/sshd_config

i can say VPN = ON => Plesk Migrator is working / VPN OFF = Plesk Migrator is not working.
i can't get the associations. i think the Port 22 for SSH is blocked and the error message is miserable and had confused me.

 

[Maarten.]

Well, you need access over SSH to start a migration. If that's blocked, you get that error message.

Just to be sure: is there only 1 "PermitRootLogin" line in the ssdh_config? If there are two or more, the last one takes precedence.

 

[Kaspar@Plesk]

I had to use a VPN service to open the ports I needed, but I thought everything goes from server A to server B without my own laptop.

Migrations are point to point (target server connects to source server). I am not sure why connecting your VPN allows to you to migrate.

Any way, the "Can not connect to the Plesk database" can be caused by the skip-name-resolve parameter in the MariaDB configuration. You can try to disabled the parameter (comment it out in /etc/my.cnf) on both servers to see if that solves the issue.

 

[Jan Bludau]

There was no connection possible via ssh, i.e. port 22, so VPN helped me!

The startup routine should check better whether ssh is actually accessible tail -f /var/log/auth.log