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

Resolved Failed to check SSH Connection to the source Server 'source'

linuxKurt

Basic Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian 18.0
This is a continuation of my efforts to migrate from a CentOS 6 server to a Ubuntu 22.04 server. I had this issue before and it was resolved via host provider and a PLESK ticket which I do not have access to. I am working with my Host Provider to try and get that information. I believe the basic issue is that the "target" cannot negotiate a connection with the "source". We are using an ECDSA Key as previously mentioned RSA keys were not working. I think the core issue is that although we have a valid ECDSA key and Public Key, the negotiation is failing. Below is the error message I see when I try to kick off a migration.

1683379245705.png
 
Have you tried using telnet to ensure your ports 21/22 are open and listen to the firewall?

These errors cause time out or couldn't connect without the port open.
 
Have you tried using telnet to ensure your ports 21/22 are open and listen to the firewall?

These errors cause time out or couldn't connect without the port open.
Thanks, I was able to work thru the above error, but the core issue still exists. I am getting the below error now, unable to negotiate. This is the reason in the past where we went to using ecdsa key, but for some reason, the source server is not able to validate or something like that. The public key is definitely in /root/.ssh on source server

Unable to negotiate with xx.xx.xx.x port 22: no matching host key type found. Their offer: ssh-rsa,ssh-dss

1683380838250.png
 
This issue is resolved. Using ECDSA key and I am not 100% sure, but I think it was updating the config and sshd_config that did it.

Thanks a lot for a tipp, generation of ssh key type ECDSA helped me.

Code:
ssh-keygen -b256 -t ecdsa -f ~/.ssh/id_ecdsa_key -q -N ""

After adding the key to source host, all worked fine.
 
Back
Top