Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Not sure, what wrong here, just some thoughts.

systemctl reload sshd.service reloads the configuration - no need to restart the service.

Changing the port in /etc/ssh/sshd_config is sufficient.

How does the output of nmap localhost looks like?

Moreover, but that is not related to the simple fact that ssh should listen on port 50687, you need to tell you firewall to let packets through and tell SELinux not to block the activity: `semanage port -a -t ssh_port_t -p tcp 50687

Not sure, what wrong here, just some thoughts.

  • systemctl reload sshd.service reloads the configuration - no need to restart the service.

Changing the port in /etc/ssh/sshd_config is sufficient.

  • How does the output of nmap localhost looks like?

  • Moreover, but that is not related to the simple fact that ssh should listen on port 50687, you need to tell you firewall to let packets through and tell SELinux not to block the activity: `semanage semanage port -a -t ssh_port_t -p tcp 50687

Not sure, what wrong here, just some thoughts.

  • systemctl reload sshd.service reloads the configuration - no need to restart the service.

  • Changing the port in /etc/ssh/sshd_config is sufficient.

    • How does the output of nmap localhost looks like?

    • Moreover, but that is not related to the simple fact that ssh should listen on port 50687, you need to tell you firewall to let packets through and tell SELinux not to block the activity: semanage port -a -t ssh_port_t -p tcp 50687