• 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.

Question Problems with ssh / Migrator / Keys

ford

New Pleskian
Server operating system version
Ubuntu 22.04.3 LTS
Plesk version and microupdate number
18.0.55
Hi,

I translate with google.

Hi,

I have 2 V servers here, an older one with a root password, a newer one with an SSH key as a password.
So far access to both with Putty or Winscp has worked well.
Now I wanted to migrate something from the newer one to the other one using an ssh key.
That's what this was needed for

Unfortunately this is the only result:

/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
[email protected]: Permission denied (publickey).

The problem is that since then I can no longer access the source server via Putty or Winscp, only an error message with the PivatKey.

No supported authentication methods available ( server sent public key )

How can I fix it if I can no longer log in via Putty or Winscp, the same error occurs via the terminal in Plesk.

Greeting
Michael
 
I understand that you can no longer access a server through SSH. In that case you may get support from your datacenter. They can attach a console to the server so that you can work on it through that console as if you were in front of the server at the data center. From there you can also restore the SSH configuration so that you can login again.
 
Back
Top