Changing SSH port, FQDN and cluster communication


New Member
Dec 22, 2022
For various reasons, one may want to change the SSH port. No security debate: it may be enforced by company policies and there's no reason to fight it from my perspective.

The cluster manager documentation mention the port 22 is expected for ssh, but how does it connect to the host? Is it a simple call to the debian provided openssh binary? Would the call honor the configuration file and use another port if specified by ~/.ssh/config?
Can it be assumed PVE7 will always use the root account for these tasks?

If honored, are the connections targeting the nodes by FQDN or IP addresses? Preparing Nodes section of the documentation recommends "referencing nodes by their IP addresses in the cluster configuration", does it mean the connection will use FQDN or IP depending on if I used FQDN or IP to add nodes to the cluster? Corosync part of the documentation correctly specify the FQDN will be resolved and stored as an IP address in the configuration file but will honor FQDN if part of the configuration file due to manual change or old version upgrade.


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 your own in 60 seconds.

Buy now!