Can't connect to shell from web ui after change ssh port

[ardyan1626]

Hi,

I have issued can't connect to shell another node pve cluster after I changed ssh port with custom port

 

[aaron]

Change it back to the expected default?

Changing the port to a non-default one is not the great addition to security. Not exposing it to the wide internet would be the better approach if that was the reason you changed it in the first place.

 

[Daniel-Doggy]

Changing any port to a non standard port is NOT SUPPORTED for this exact reason.

 

[ardyan1626]

But in my company security policy must change the SSH default port to a custom port

 

[aaron]

Well, changing the SSH port will break more than just access to the host shell via the web UI. Live migrations are one such thing I can think of.

Can you work around that in some situations and override the default port to connect to? Probably yes. Will it be supported from our side if you run into issues? No.

But in my company security policy must change the SSH default port to a custom port

Then it might be time to re-evaluate these policies, or make exceptions.
An example regarding policies; it is by now discouraged to force users to change their passwords regularly.

From a technical perspective, changing the default SSH port is of questionable gained security… A full port scan is done quickly.