Configuring a Custom SSH Port
Users with the SysAdmin role or an enabled superuser flag can change the SSH port from the default, which is port 22, to some other. The new port becomes active for all incoming SSH connections. The Command Center will receive data on the new port you specify. This change is useful to customers who would like to log in to the CLI on a port they specify.
| Method | API Command | CLI Command |
|---|---|---|
| GET SSH Port | GET /api/rest/management/sshport | system ssh |
| SET SSH Port | GET /api/rest/management/sshport?port=<port> | system ssh <port> |
Valid port values are from 0 to 65535 inclusive. If you change the port value to one already in use by another service, an error message will be returned. Use the new port value to access CLI, for example, or copy files to the Lumeta system from a remote client.
Some CLI commands allow you to upload files from remote machines running SSH. These commands can take an optional port number that is useful when the SSH server does not or should not use the default port 22.CLI Command Example collector discoveryspaces c1 target + remote user@host:path/to/file 11111
system configuration import user@host:path/to/file 11111
system configuration export user@host:path/to/file 11111
system upgrade user@host:path/to/file 11111
support diagnostics user@host:path/to/file 11111
zone discoveryspaces zname listtype opt remote user@host:path/to/file 11111
These CLI commands have been updated to support a custom SCP port number and are expected to be made available in a near-term release:CLI Command Example certificate lumeta install user@host:path/to/file 11111
certificate ca install user@host:path/to/file 11111
certificate ssh install user@host:path/to/file 11111 user
certificate server install user@host:path/to/file 11111 friendlyName password
certificate crl install user@host:path/to/file 11111
certificate user install user@host:path/to/file 11111 user