• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Plesk Migration tool ( Migrating between GoogleCloudPlatfrom)

###########################
Port 22
PermitRootLogin yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
UseDNS no
AllowUsers root
###########################


How can i edit this permissions? via ssh? can you give me sample codes?
 
I would use this command on the new server to create your key pairs. Not sure why "protocol 1" is even coming up in the screenshot you posted:

On the new server:

su root

ssh-keygen -b 2048 -t rsa -f /root/.ssh/mynewkey

<hit return and use NO passphrase>

Manually copy the contents of /root/.ssh/id_rsa.pub on the NEW server to the /root/.ssh/authorized_keys file on the OLD server.

If your old server is also a GCE, you may need to enter the "root" usernames and keys here:
Google Cloud Platform

On both machines, make sure the /root/.ssh/ folder has chown root:root permissions and chmod 700

On both machines, make sure the contents of /root/.ssh/* folder has chown root:root permissions and chmod 600

On both machines, do:
service sshd restart

From the command line of the new server, you should be able to log directly in to the old server using this command:
ssh -24kv -l root 35.227.27.42 -p 22

If you can't log in directly like this, Plesk will not be able to either.
 
h4ZhZx


where is my root password? same with plesk?

Screen Shot 2018 04 10 at 02 25 40

i changed passwd . via sudo passwd code..

and this is the new ss .

Screen Shot 2018 04 10 at 02 32 41
 
Last edited:
/root/.ssh/id_rsa.pub .

When i enter this code in ssh window showing this error:

Code:
[root@gcp-plesk-vm-1-vm furkanbaser]# /root/.ssh/id_rsa.pub
bash: /root/.ssh/id_rsa.pub: No such file or directory
[root@gcp-plesk-vm-1-vm furkanbaser]# /root/.ssh/id_rsa.pub

How can i move or copy to metadata place in manually? i dont know what part of a copy?
 
/root/.ssh/id_rsa.pub .

When i enter this code in ssh window showing this error:

Code:
[root@gcp-plesk-vm-1-vm furkanbaser]# /root/.ssh/id_rsa.pub
bash: /root/.ssh/id_rsa.pub: No such file or directory
[root@gcp-plesk-vm-1-vm furkanbaser]# /root/.ssh/id_rsa.pub

How can i move or copy to metadata place in manually? i dont know what part of a copy?

try:
sudo cat /root/.ssh/id_rsa.pub

then cut and paste it from your terminal.
 
How many sites do you need to migrate?
If they are not too much, why just don't archive site by site and restore backups in new machine
 
Back
Top