Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Customer updated Host server resulting in new host key

What kind of server is that? What kind of upgrade was it?

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=C:\path\to\winscp.log command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
Jtomalewski

Customer updated Host server resulting in new host key

We run a simple batch script using WinSCP to connect to our customer servers and pull files over using private/public key. Recently a customer ran updates in their environment resulting in a new hostkey. Going through the GUI I receive the prompt similar to below, and accept the new key.
https://winscp.net/eng/docs/message_host_key

When connecting through our commandline I receive the error "Server's host key did not match the signature supplied"

Command we're running 
"C:\program files (x86)\winscp\winscp.com" /command "option confirm off" "open username@hostname -privatekey=privatekey.ppk"

Output is 
confirm      off

searching for host...

connecting to host...

Server's host key did not match the signature supplied.

I've tried adding the -hostkey switch into the open command using every variation of -hostkey=* or -hostkey=""ssh-rsa XXXXXXXXX"". All of which results in the same error. How can I get past this issue.

Documentation

Support

Associations

Follow Us