Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Secure FTP (FTPS) server that my remote sites to upload files to daily via scripted routines that run. I have had issues in the past when upgrading hardware and deploying new servers causing the RSA Fingerprint to change for that server. Then all my remote sites can't connect until I have the old key removed (usually via ssh_keygen -r

I now have to change the IP address for and I wondered if there is anyway to proactively generate new host keys so that when the server address changes all my FTPS client remote sites don't break?

share|improve this question
up vote 1 down vote accepted

(I think you mean sftp, not ftps. Ftps has nothing to do with SSH.)

The answer is "no." Think about it from a client's perspective: how can a client trust that they are actually communicating with the correct server rather than a rogue server? If the server was allowed to change IPs (or keys) at will with no complaint from the client then the client would happily connect to a rogue server.

It's inconvenient, but you should coordinate the change in IPs out of band. E.g., a secure email stating "At X time the server's IP will change to Y; you will need to update your client's key store." In reality, that may be too inconvenient so ssh clients offer some configuration options to reduce security. For example, OpenSSH has the option CheckHostIP which, when set to no disables IP checking. Still, it is in the client's hands, not the server's, to decide whether to trust the server or not.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.