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

jhonnytay

Member
Aug 24, 2020
22
0
21
41
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:

About

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!