After Server Upgrade, Needing Help Updating SSH Keys Settings

Hello, our website's server was recently updated to something newer (from CentOS 7). And normally, I connect to this server over SSH (using Windows PowerShell). And after going through a process of creating new public/private keys and installing them on my computer plus creating a new passphrase, etc., now everything is working just fine on that side.

So next I attempted connecting to the server using WinSCP, and at first I saw a prompt with the option to 'Update' my settings – which I did. I was expecting to see a password prompt after that, where I'd put in the new password and be in ...

But unfortunately, that's not what happened. Instead, I saw this message (and see it every time I try connecting now):

No supported authentication methods available (server sent: publickey)

Authentication log (see session log for details):
Using username "myusername".

Authentication failed.

I think the issue is that the previous private key lived on my computer in a different location from where the new key is ... But after spending over an hour reading online documentation and trying a few things, nothing is working for me.

Note: I am doing this with a computer running 'Windows 11 Home' and am also on the latest version of WinSCP.

It's probably an easy fix, but I'm finding it hard to figure out and therefore any assistance will be appreciated!

Thanks,
Jim

Okay, after parsing the documentation some more, I think I've figured it out. As follows:

1. First, the docs don't say this, but you can't edit an existing session and get to the 'Advanced' tab. So you have to create a new workspace – not entirely an intuitive step when the existing workspace is correct and you just need to update the path to the private key.
   
   
2. On the Advanced > Authentication dialog, once you select the .ppk file and load it into the dialog, another field opens to enter a certificate for that private key. I don't see in the documentation anything about whether you need to enter this or not. But in my case, I did not and it turns out to not be required (at least in my case), for what it's worth.
   

After doing that and then clicking 'Log in', the authentication *did* work and I was prompted to enter the new password. After doing so, I was logged into the server as per normal.

So in the end, it was very easy once you figured out how to do it. Unfortunately, as much as I appreciate the WinSCP documentation, I feel like it was too much general info. And not enough specific 'step-by-step' instructions for how to do this.

As such, I probably spent about 2+ hours on this when it should have been about 15 minutes. Anyway, hopefully this might help someone else sometime.

Thanks for sharing your experience.

Few notes:

• You can edit an existing stored site. Just select it in the tree on the left and press Edit button:
  https://winscp.net/eng/docs/ui_login#edit
  If you had just an ad-hoc session [not saved] opened in workspace, then indeed that cannot be edited on the Login dialog.
  (though you can open the workspace, save the ad-hoc session to a site and then edit it)
  I have added this to the tracker:
  Issue 2461 – Allowing working with individual sessions of a workspace on Login dialog
  
  
• Instructions for setting up and configuring public key authentication are here:
  Set up SSH public key authentication