SSH to the CPM instance fails after upgrade to CPM 4.2.x with "Server refused our key"

Problem:   After upgrading the CPM instance to version 4.2.x, when you try to SSH to the server with PuTTY it may fail with the error "Server refused our key": 

 

Resolution:    CPM 4.2 upgrades the version of Ubuntu to 22.04.  This requires you to be using the latest version of PuTTY.  As of this writing, build 0.79 is the latest release and will fix the issue.  You can find the latest version at https://www.putty.org/ 

• Related Articles

• How to upgrade an N2WS server from Ubuntu 18 to Ubuntu 18 Pro

  Before starting, make sure you know how to redeploy the server in case of issues during OS upgrade. In addition, Linux knowledge is Required. There are additional costs charged by AWS when using Ubuntu Pro, see this link for pricing details. Warning: ...

• Upgrade fails with error "Could not mount the new volume, returned: 8192"

  If you get this error message during an upgrade, it is very likely that the filesystem is corrupted on the CPMData Volume. Please perform these steps: 1) Connect to N2WS EC2 instance where the upgrade failed using user "cpmuser" and your Key 2) ...

• How to connect to an instance in AWS using SSH

  This article will walk you though how to connect to your CPM instance using SSH, these steps can also be used to connect to any Linux instance in AWS including a CPM worker instance. The same process and key is used for an SSH connection to CPM or a ...

• CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors

  CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist"  and "Configuration Failed" errors: The reason for this failure is using wrong AWS Access Key and Secret Key - maybe they belong to the wrong account.

• Upgrade instructions for v3.x/4.x

  This guide outlines the steps required to upgrade to N2WS Backup & Recovery version 3.x/4.x We strongly recommend that you follow every step contained within this guide to ensure version 3.x/4.x is configured correctly and no data loss occurs. ...