ssh hostkeys

  1. I

    2025 / PVE9.x / WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! [analysis, resolution]

    I got tired of running into this issue on every PVE version. I spent some time deep diving to get this to reproduce consistently. Related threads: 2025 - Enable RSA key seems to fix 2023 - SSH Host key ceritificates 2022 - Remote host identification has changed Test Setup: PVE 9.0 / 3 node...
  2. C

    [SOLVED] WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

    This issue has been resolved. A former sysadmin disabled the ssh-rsa host keys. They have been re-enabled and the problem has been solved. While investigating this issue, it was discovered that Proxmox prefers broken keys (ssh-rsa) over less-broken keys (ed25519). I have ALREADY reviewed the...
  3. D

    cloud-init and ssh hostkeys

    After removing the hostkeys from /etc/ssh and generating a template, cloud-init generates new hostkeys according to /var/log/cloud-init-output.log but the keys are not written to /etc/ssh/. Because there are no hostkeys, ssh.service does not start. I can get around this by using the noVNC shell...