Setting up an OpenSSH Server for Rsync on Ubuntu Linux to Support Windows 11

To enable Rsync file transfers from Windows 11 to an Ubuntu OpenSSH server, you must use a compatible Rsync client such as Git Bash or WSL, since native Windows does not include the rsync executable. Install OpenSSH on Ubuntu, generate SSH keys for secure authentication, and configure the server to accept key-based logins. This setup allows seamless, encrypted synchronization of files between your Windows machine and Linux environment without relying on third-party FTP services.

Installing and Configuring OpenSSH on Ubuntu

The foundation of this connection is a properly configured OpenSSH server on your Ubuntu machine. By default, many cloud images and desktop installations do not have the SSH daemon running or accessible. You need to install the package, enable it to start on boot, and ensure the firewall permits incoming connections on port 22. First, update your package list to ensure you have the latest security patches. Then, install the OpenSSH server using the standard package manager. After installation, enable the service so it persists across reboots. Finally, verify that the service is active and listening. If you are using UFW (Uncomplicated Firewall), which is common on Ubuntu Desktop, you must explicitly allow SSH traffic.

sudo apt update
sudo apt install openssh-server
sudo systemctl enable ssh
sudo systemctl start ssh
sudo ufw allow OpenSSH

Once these steps are complete, you should be able to test the connection from another Linux machine or via PowerShell using ssh user@ubuntu_ip. However, for Rsync to work efficiently with Windows 11, we will move away from password authentication in favor of public-key cryptography.

Generating SSH Keys for Authentication

Password authentication is often cumbersome for automated tools like Rsync and poses security risks if weak passwords are used. Generating an SSH key pair allows Windows to authenticate with Ubuntu without exposing your password over the network. You can generate these keys directly within the Git Bash or WSL environment installed on your Windows 11 machine. Open Git Bash or your preferred terminal emulator. Run the ssh-keygen command. It is recommended to specify the type of key as ed25519 for better security and performance, though RSA is also widely supported. When prompted for a file name, you can press Enter to accept the default location, typically ~/.ssh/id_ed25519. For added security, set a passphrase for the private key, although you may skip this if you require fully unattended scripts.

ssh-keygen -t ed25519 -C "[email protected]"

After generating the key, you must copy the public key to your Ubuntu server. The most reliable method is using the ssh-copy-id utility. This tool automatically appends your public key to the ~/.ssh/authorized_keys file on the remote host. Replace username and ubuntu_ip with your actual credentials.

ssh-copy-id username@ubuntu_ip

If ssh-copy-id is not available in your specific Windows terminal, you can manually copy the content of ~/.ssh/id_ed25519.pub and append it to the same file on the Ubuntu server. Ensure the permissions on the Ubuntu side are correct: the .ssh directory should be 700, and the authorized_keys file should be 600.

Configuring the OpenSSH Server for Security

With keys generated, you need to harden the OpenSSH configuration to prevent unauthorized access. Edit the main configuration file located at /etc/ssh/sshd_config on your Ubuntu system. While modern versions of OpenSSH disable root login by default, it is crucial to verify this setting. Additionally, you should enforce protocol version 2 and disable password authentication entirely if you only intend to use keys. Find the line containing PermitRootLogin and change it to no. Locate PasswordAuthentication and set it to no. These changes ensure that even if someone guesses your password, they cannot log in, and brute-force attacks against the root account are blocked.

sudo nano /etc/ssh/sshd_config

# Change these lines:
PermitRootLogin no
PasswordAuthentication no

After saving the file, restart the SSH service to apply the changes. Test the connection from your Windows machine again to ensure you can still log in using your new key. If you encounter permission denied errors, check the Ubuntu journal logs using journalctl -u ssh for detailed diagnostics. For more troubleshooting on connectivity issues, see Unable to Submit Files via Rsync on Ubuntu VPS.

Running Rsync from Windows 11

Windows 11 does not include a native rsync.exe binary. Attempting to run rsync in Command Prompt or PowerShell will result in a "command not found" error. To resolve this, you must use one of two primary methods: Git Bash or Windows Subsystem for Linux (WSL). Both environments provide a Linux-compatible shell and the necessary binaries. If you have Git for Windows installed, open Git Bash. Navigate to the directory containing the files you wish to transfer. Use the rsync command with the -avz flags for archive mode, verbose output, and compression. Specify the source path and the destination in the format user@host:/path/to/destination.

rsync -avz /local/path/ username@ubuntu_ip:/remote/path/

Alternatively, if you are using WSL, you can run the command directly from the WSL terminal. WSL provides a full Linux kernel interface, making it highly compatible with standard Linux tools. Note that when accessing Windows files from WSL, you must reference them under the /mnt/c/ mount point (for the C drive).

rsync -avz /mnt/c/Users/YourName/Documents/ username@ubuntu_ip:/home/user/backup/

This approach ensures that the data transfer is encrypted via SSH and leverages the efficiency of Rsync's delta-transfer algorithm, sending only changed parts of files.

Handling Large Transfers and Permissions

When transferring files, ownership and permissions might not be preserved correctly depending on how you invoke the command. To preserve timestamps and permissions, the -a flag is essential. If you are syncing directories owned by different users, you may need to run the Rsync command with elevated privileges on the Ubuntu side or adjust the rsync options to handle ownership carefully. Always perform a dry run first by adding the --dry-run flag to verify what would be transferred before committing to the actual operation.

Frequently Asked Questions

Can I use PowerShell Core to run rsync?

No, PowerShell Core does not include the rsync binary natively. You must rely on external tools like Git Bash, Cygwin, or WSL to provide the Linux-compatible rsync executable. Attempting to download standalone rsync executables for Windows often leads to dependency issues and is not recommended.

Why is my rsync command hanging or timing out?

This usually indicates a firewall blocking port 22 or a network routing issue. Verify that Ubuntu's UFW or iptables rules allow inbound SSH traffic. Additionally, ensure that your Windows firewall is not interfering with outbound connections to the Ubuntu IP address.

How do I sync files bidirectionally?

Standard rsync is unidirectional, copying from source to destination. For bidirectional synchronization, consider using tools like Syncthing or FreeFileSync, which are designed to keep two directories in sync regardless of which side initiates the change. Rsync is best suited for backups or one-way transfers.

What if I forget my SSH key passphrase?

If you set a passphrase on your SSH key, you cannot recover it. You will need to generate a new key pair and update the authorized_keys file on the Ubuntu server. To avoid this in the future, consider using an SSH agent to cache your passphrase temporarily during your session.

Is it safe to disable password authentication?

Yes, disabling password authentication is a security best practice known as "hardening." It prevents brute-force attacks that attempt to guess passwords. As long as your private SSH key is kept secure and backed up, key-only authentication is significantly more secure than password-based login.