How to Change the SSH Port (2024)

SSH, or Secure Shell, is an essential protocol for securely accessing and managing remote servers. It encrypts all communication, ensuring that data remains protected from unauthorized interception.

By default, SSH runs on port 22, which is often targeted by brute force attacks. Changing the default SSH port can significantly enhance security by reducing the likelihood of automated attacks.

This article will guide you through all the steps to changing the SSH port on a Linux virtual private server (VPS), from selecting the appropriate new port to ensuring your server remains accessible after the change.

Download ultimate SSH commands cheat sheet

Choosing a New SSH Port

It’s important to select a port that is not already in use by other services to avoid potential conflicts and reduce security risks on your VPS. Here are some of the most commonly used port numbers with their associated services and protocols:

Additionally, consider selecting a port outside the well-known range (0-1023) and the registered ports range (1024-49151). It’s advisable to opt for a custom port within the dynamic or private ports range (49152-65535).

How to Change the Default SSH Port

Now that you chose a new port, let’s proceed with the steps to implement the change.

1. Access Your Server via SSH

Before you can make any changes, you need to access your server securely. Follow these steps to connect to your server via SSH:

1. Whether you’re using Windows, macOS, or Linux, start by opening a new terminal window. On Windows, you may need an SSH client like PuTTY.
2. Use the following command to connect to your server. Replace username with your actual server username and server_ip with your server’s IP address:

ssh username@server_ip

3. Enter the password associated with the username you provided. For enhanced security, it is recommended to use SSH keys instead of passwords.

2. Edit the SSH Configuration File

Once you’ve successfully accessed your server, the next step is modifying the SSH configuration to use a new port. This involves editing the sshd_config file, which controls various parameters of your SSH daemon.

1. Use the following command to open the SSH daemon configuration file in the nano text editor:

sudo nano /etc/ssh/sshd_config

2. Scroll down until you find the line that includes #Port 22. This line is commented out by default, and the number 22 represents the default port.
3. Remove the # to uncomment this line and change 22 to your desired port number, such as 61189.

4. Once done, press Ctrl + X → Y → Enter to save the changes and exit nano.

3. Adjust Firewall Settings

After updating your SSH port, it’s essential to adjust your firewall settings to allow traffic on the new port. However, if you’ve never configured any firewall rules, you can skip this step and proceed to the next section.

Here’s how to update firewall settings using Uncomplicated Firewall (UFW):

1. Execute the following command to allow incoming connections on your new port over TCP, replacing 61189 with your specific port:

sudo ufw allow 61189/tcp

2. Reload UFW to apply the changes:

sudo ufw reload

For Hostinger’s VPS hosting customers, you can easily configure firewall settings on hPanel. Follow these steps:

1. Access your VPS dashboard and navigate to Settings → Security → Firewall.
2. Click Create firewall configuration, name your new configuration, and click Create.

3. Click the three-dot horizontal button and choose Edit.

4. In the Add firewall rule section, configure the rules you prefer and click Add Rule.

5. Return to the Firewall page and click Activate.

After setting up your firewall rules using either method, verify the current UFW status with this command:

sudo ufw status

4. Restart the SSH Service

Once you’ve updated the SSH configurations and firewall rules, it’s time to restart the SSH service to apply the new settings.

For systems using systemd, which is common in newer distributions like Ubuntu, Debian, and CentOS, restart the SSH service by running the following command:

sudo systemctl restart sshd

For older systems that use SysVinit, use this command instead:

sudo service ssh restart

After restarting, verify the SSH service status to make sure everything is running smoothly:

sudo systemctl status sshd

5. Verify the New Port

Now that you’ve restarted the SSH service, the final step is verifying that SSH is indeed operating on the new port. This ensures that your changes have been successfully implemented and the server is accessible.

Check the SSH Port with ss or netstat

If you have ss installed, use the following command to list active connections, filtering for your new SSH port:

ss -tuln | grep [new_port_number]

Here’s the output you might see:

If you prefer using the netstat command, you can check with:

netstat -tuln | grep [new_port_number]

The output should resemble:

Log In Using the New Port

Open a new terminal window to test connecting to the server with the new SSH port number by executing this command:

ssh -p new_port_number username@server_ip

Replace new_port_number, username, and server_ip with your specific details.

A successful SSH connection using the new port confirms that your server is functioning correctly with the changes.

Important! Do not log out of your previous root session until you’ve confirmed that the new setup is working correctly.

Conclusion

Changing the default SSH port is an effective security measure that can reduce your server’s vulnerability to attacks.

By implementing this change along with other best practices, such as using firewalls, regularly updating server packages, and setting up multi-factor authentication, you create a more secure environment for your SSH server.

Remember, security is an ongoing process that benefits from regular attention and adaptation.

How to Change the SSH Port FAQ

This section will answer the most common questions on how to change the SSH port.