Auto-generated ssh key and authorized_keys


New Member
May 4, 2016
Hi everyone!

I just noticed that on a freshly installed Proxmox node the root user already comes with the .ssh folder. Into /root/.ssh there is the pair id_rsa/, a config file and the authorized_keys, that is a symlink to /etc/pve/priv/authorized_keys.

Within this file, the root's public key is pre-loaded. If I delete it, it reappears upon reboot. If I delete the root's ssh key, it's generated again and the public one is stored inside /etc/pve/priv/authorized_keys.

What's the purpose of this mechanism? Is it a good idea to disable it? If so, how?
We use this to connect to other nodes via ssh (for example when you migrate a VM to another cluster node).
Ok, so there's no point for me in using it.
How can I disable the feature, making both key removal and the change to authorized_keys permanent?
So, is it really impossible to disable this mechanism?

it is needed for cluster functionality. it makes more sense to disable SSH access from the public or from non-cluster nodes on the firewall level
Increasing the FileZilla timeout from default 20 secs to 40 secs just cleared the issue.

Made sure the /etc/resolv.conf had a local nameserver.
Other means that may be used to troubleshoot SFTP issues and SSH login delays are at:

How to fix a slow SSH login issue on Linux

The attachment too will be useful in mitigating this issue.

Looks like the PVE 3.4 is okay after all.


  • Speedup sshd logins.pdf
    193 KB · Views: 36


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!