Linux – Cannot log in to server after SSH port change

linuxportssh

I followed step one of this guide to change the SSH port of my server: http://www.linux.com/archive/articles/61061

Now, when I try to log in to it again by typing

    ssh -p 1234 user@my-server

I get the message

    Connection closed by xxx.xxx.xxx.xxx

xxx being the IP address of my server.
Not using the -p option of using any other port results in the answer

    ssh: connect to host my-server.com port xxx: Connection refused

How can I connect to it again? It's a Debian machine, in case that matters.

Best Answer

(As Kurt just mentioned) After having changed your default port in sshd_config, did you follow up by ensuring iptables was allowing inbound connections to your new port?

Related Solutions

Ssh – how to make standard ssh port a stealth port

The server is not sending anything, it's the client telling you the server refused the connection. That's the expected behaviour if a TCP port is closed when you try to connect.

If you want your system to silently drop packets without sending a "this port is closed" TCP answer (a so-called stealth port), you need to use a firewall on the system and/or in between it and the client.

Windows – Is the password compromised because I forgot to hit Enter after ssh username

In short: yes.

# ssh 192.168.1.1 -l "myuser mypassword"
^C
# egrep "mypassword" /var/log/auth.log
Oct 19 14:33:58 host sshd[19787]: Invalid user myuser mypassword from 192.168.111.78
Oct 19 14:33:58 host sshd[19787]: Failed none for invalid user myuser mypassword from 192.168.111.78 port 53030 ssh2

Best Answer

Related Solutions

Ssh – how to make standard ssh port a stealth port

Windows – Is the password compromised because I forgot to hit Enter after ssh username

Related Topic