Issue Root login and root password in Plesk Migrator

[DigitalSplendid]

Server operating system version

Ubuntu 18.04.4 LTS

Plesk version and microupdate number

Plesk Obsidian v18.0.48_build1800221104.10 os_Ubuntu 18.04

Facing trouble figuring out root login and root password while migrating Plesk from one AWS account to another. Is it the same username/password used to login to Plesk Admin? Help appreciated.

 

[Peter Debik]

This is the system's "root" user that you'd use to sign on to the operating system as "root". The password is the password of that root user.

 

[DigitalSplendid]

Thanks!
If I understand correctly, in Root login field, I need to enter root.
And how do I recover password?

 

[Peter Debik]

The root password of your server has been set on setup by your provider (or yourself). You cannot recover the root password. You can only change the root password after you are logged on as root or have escalated your privileges by "sudo" or "su" from your user account on the shell.

 

[DigitalSplendid]

Thanks for the prompt reply. What should I type on shell to change password?

 

[Kaspar]

Google: How to change Root password on Ubuntu

 

[DigitalSplendid]

Google: How to change Root password on Ubuntu

I understand the below command needs to be entered into SSH with Lightsail.

sudo passwd root

As I entered the above command, the screen becomes unresponsive and I am unable to enter any text/number.

 

[Peter Debik]

the screen becomes unresponsive and I am unable to enter any text/number.

It is possible that the cursor does not move, but you can still enter something. Simply hit "Enter" when you are done and you'll see the prompt to repeat the password.

 

[DigitalSplendid]

It is possible that the cursor does not move, but you can still enter something. Simply hit "Enter" when you are done and you'll see the prompt to repeat the password.

Thanks for the support.

Attached are the screenshots while trying to migrate. Not successful and help appreciated.

 

[Peter Debik]

As I understand the error message on the last screenshot, the source only allows SSH login through public key, but not through user/password authentication. Does this help?

https://support.plesk.com/hc/en-us/articles/115000065489-How-to-set-up-SSH-keys-for-Plesk-server-

Please be careful when changing authentication mechanism so that you do not lock yourself out from your server.

 

[DigitalSplendid]

Thanks for the support.

I tried using SSH. After entering
ssh-keygen -t rsa -b 2048
/root/.ssh/id_rsa
I am asked to enter passphrase or keep it empty. Opted for empty by Enter button on keyboard. This is the error message:

Saving key "/root/.ssh/id_rsa" failed: Permission denied

 

[Peter Debik]

According to your screenshots you are logged in with a normal user. You must be "root" in order to overwrite or create such files. So first escalate your privileges to root, e.g. "sudo su -" or "su", depending on how the system is configured.

 

[DigitalSplendid]

After logged in as root user, I tried the above process. Getting this error message:

Failed to check SSH connection to the source server 'source' (13.234.179.212).

Attached are the screenshots.

Thanks in advance!

 

[Peter Debik]

Ensure that the server is up and there are no firewall rules that may block SSH connections to the server, then restart migration. I'd also suggest to try to use key login through an SSH client such as PuTTY so that before you try the migration with it, you can be sure that you can really login to the source using the key.

 

[scsa20]

Hi DigitalSplendid. Can you check your AWS's security group to make sure that SSH port 22 isn't limited to just your IP? You'll want to make sure it's either open (not safe) or include the IP address of your new server. Since you're going from one AWS instance to another, if they're in the same VPC and have a private IP address within the same subnet, you could save yourself the hassle with the security groups by using the private IP address instead for the connection.

Also, depending on your AWS instance, the username could be different so you'll want to check that out as well. Usually, by default, you will not be able to log into the root account itself via SSH (although using the console you can) which looks like is what you're doing). If I recall correctly, when I migrated out of AWS I used the normal ec2-user account just fine for the migration.

Just a few things to check.

 

[DigitalSplendid]

Hi DigitalSplendid. Can you check your AWS's security group to make sure that SSH port 22 isn't limited to just your IP? You'll want to make sure it's either open (not safe) or include the IP address of your new server. Since you're going from one AWS instance to another, if they're in the same VPC and have a private IP address within the same subnet, you could save yourself the hassle with the security groups by using the private IP address instead for the connection.

Also, depending on your AWS instance, the username could be different so you'll want to check that out as well. Usually, by default, you will not be able to log into the root account itself via SSH (although using the console you can) which looks like is what you're doing). If I recall correctly, when I migrated out of AWS I used the normal ec2-user account just fine for the migration.

Just a few things to check.

 

[DigitalSplendid]

I have checked port 20-22. All seems open.