PVE 6.3-2 cluster node connection refused after default SSH port changed

jhonnytay

Active Member
Aug 24, 2020
23
0
41
42
Dear Support,

Was wondering why each nodes were become unable to connect upon I changed the default SSH port from 22 to other.

Best Regards,SSH-Connection-Refused.PNG
 
Was wondering why each nodes were become unable to connect upon I changed the default SSH port from 22 to other.
ssh is used in quite a few cases by PVE for communication between cluster nodes. It also expects to not have to pass a specific port

you could try to add a different default port to the ssh client config on each node (/etc/ssh/ssh_config) - this should be enough in theory.

I hope this helps!
 
  • Like
Reactions: Beno Ben
Hello everyone,
I had the same problem. In my case it was true to change the default connection port to (/ etc / ssh / sshd_config).
 

Attachments

  • Screenshot_50.png
    Screenshot_50.png
    18.8 KB · Views: 25
  • Like
Reactions: bhatmag1ck
I had a similar problem, but I assign different SSH ports for each node. So to SSH from Proxmox on the web interface's shell to another node, I config the source node's ~/.ssh/config file to the destination node's SSH port. An example config of a remote host is shown below:
Code:
Host 192.168.1.3
    User root
    Port 65536
 
Last edited: