Fix: Tabby SSH Fails To Connect To GL-iNet/OpenWRT

Nov 13, 2025 by Alex Johnson 51 views

Troubleshooting Tabby's SSH Connection to GL-iNet/OpenWRT Devices

Experiencing issues connecting Tabby to your GL-iNet/OpenWRT device? You're not alone. This guide will walk you through diagnosing and resolving the "Authentication rejected" error when using Tabby to SSH into your device. We'll cover common causes, troubleshooting steps, and alternative solutions to get you connected.

Understanding the Problem

The core issue is that Tabby, a terminal emulator, is failing to authenticate with your GL-iNet/OpenWRT device via SSH. This is happening despite the fact that you can successfully connect using a regular prompt or PowerShell within Tabby. The error messages you're seeing, including the host key fingerprint, indicate that the connection is being established but the authentication process is failing. This discrepancy suggests a configuration problem specific to Tabby's SSH settings or a conflict with the device's SSH server configuration.

Diagnosing the "Authentication Rejected" Error

Before diving into solutions, let's pinpoint the root cause. Here are a few key areas to investigate:

1. SSH Key Configuration

The most common reason for authentication failures is an incorrect or missing SSH key. Tabby might not be using the correct key, or the key might not be properly authorized on your GL-iNet/OpenWRT device.

Check Tabby's SSH Configuration: Verify that Tabby is configured to use the correct SSH key file. In Tabby's settings, navigate to the SSH connection profile for your GL-iNet/OpenWRT device and ensure the "Private key" field points to the correct .pem or .ppk file.
Verify Key Permissions: SSH keys have specific permission requirements. The private key file should only be readable by the user running Tabby. On Linux or macOS, you can use the command chmod 600 /path/to/your/private/key to set the correct permissions.
Authorized Keys File on the Device: Ensure that the corresponding public key is present in the ~/.ssh/authorized_keys file on your GL-iNet/OpenWRT device. If the file doesn't exist, create it. If the key isn't there, add it. Be careful when editing this file, as incorrect entries can lock you out of your device. The public key usually starts with ssh-rsa, ssh-dss, ssh-ed25519, or ecdsa-sha2-nistp256.

2. Authentication Methods

Your GL-iNet/OpenWRT device might be configured to only allow certain authentication methods. If Tabby is attempting to use a method that's not enabled, the connection will be rejected.

Password Authentication: While generally discouraged for security reasons, ensure that password authentication is enabled on your device if you're relying on it. Check the /etc/ssh/sshd_config file on your GL-iNet/OpenWRT device for the line PasswordAuthentication yes. If it's commented out or set to no, enable it and restart the SSH service.
Public Key Authentication: Public key authentication is the preferred method. Make sure it's enabled in /etc/ssh/sshd_config with the line PubkeyAuthentication yes. Also, verify that AuthorizedKeysFile .ssh/authorized_keys is correctly configured to point to the file containing your public keys.

3. SSH Server Configuration

The SSH server on your GL-iNet/OpenWRT device might have restrictions that are interfering with Tabby's connection.

Firewall Rules: Double-check that your device's firewall is not blocking SSH connections from Tabby's IP address or port. The default SSH port is 22, but it might be different on your device. Use the iptables command to inspect the firewall rules.
Listen Address: Verify that the SSH server is listening on the correct IP address. In /etc/ssh/sshd_config, the ListenAddress directive specifies the IP addresses the SSH server will listen on. If it's set to a specific IP address, make sure it's accessible from the machine running Tabby. If set to 0.0.0.0, it listens on all interfaces.

4. Tabby-Specific Issues

Sometimes, the problem lies within Tabby itself.

Tabby Configuration Errors: Review Tabby's SSH connection profile for any typos or incorrect settings. Pay close attention to the hostname, port, username, and authentication method.
Plugin Conflicts: Third-party plugins can sometimes interfere with Tabby's functionality. Try disabling any plugins you have installed to see if that resolves the issue.
Tabby Version: Ensure you're using the latest version of Tabby. Older versions might have bugs that have been fixed in newer releases.

Step-by-Step Troubleshooting Guide

Follow these steps to systematically troubleshoot the connection issue:

Verify Basic Connectivity: Use the ping command from the machine running Tabby to ensure you can reach your GL-iNet/OpenWRT device.
Test SSH Connection with a Standard Client: Use a standard SSH client like ssh from a terminal or PuTTY to connect to your device. This will help determine if the issue is specific to Tabby.
Check SSH Server Logs: Examine the SSH server logs on your GL-iNet/OpenWRT device for any error messages or clues about the authentication failure. The logs are typically located in /var/log/auth.log or /var/log/secure.
Review Tabby's Configuration: Double-check all the settings in Tabby's SSH connection profile, including the hostname, port, username, authentication method, and SSH key file.
Disable Plugins: Temporarily disable any plugins you have installed in Tabby to see if they're causing the problem.
Update Tabby: Make sure you're running the latest version of Tabby.
Restart SSH Service: Restart the SSH service on your GL-iNet/OpenWRT device to apply any configuration changes.
Factory Reset (Last Resort): If all else fails, consider factory resetting your GL-iNet/OpenWRT device and starting from scratch. This will eliminate any potential configuration issues.

Practical Solutions and Code Examples

Here are some specific solutions and code examples to address common issues:

1. Adding Your Public Key to `authorized_keys`

If your public key is not in the authorized_keys file, you can add it using the following steps:

Copy the Public Key: Copy the contents of your public key file (e.g., id_rsa.pub) to your clipboard.
SSH into Your Device (using a working method): Use a standard SSH client (like ssh from your terminal) to connect to your GL-iNet/OpenWRT device.
Edit the authorized_keys File: Use a text editor like vi or nano to open the ~/.ssh/authorized_keys file:
```
vi ~/.ssh/authorized_keys
```
Paste the Public Key: Paste the public key into the file. Make sure there are no extra spaces or line breaks.
Save the File: Save the changes and exit the text editor.

2. Enabling Password Authentication (Use with Caution)

If you need to enable password authentication, follow these steps:

Edit the sshd_config File: Use a text editor to open the /etc/ssh/sshd_config file:
```
vi /etc/ssh/sshd_config
```
Find the PasswordAuthentication Directive: Locate the line that starts with PasswordAuthentication.
Uncomment and Set to yes: If the line is commented out (starts with #), remove the # and set the value to yes:
```
PasswordAuthentication yes
```
Save the File: Save the changes and exit the text editor.
Restart the SSH Service: Restart the SSH service to apply the changes:
```
/etc/init.d/ssh restart
```

3. Checking Firewall Rules

To check if your firewall is blocking SSH connections, use the iptables command:

 iptables -L

This will list all the firewall rules. Look for any rules that might be blocking traffic on port 22 (or your custom SSH port). If you find a blocking rule, you can remove it or modify it to allow SSH connections from Tabby's IP address.

Key Takeaways

Double-check your SSH key configuration in Tabby. Ensure the correct private key is selected and that the corresponding public key is in the authorized_keys file on your device.
Verify that the necessary authentication methods (public key or password) are enabled in the /etc/ssh/sshd_config file on your GL-iNet/OpenWRT device.
Check your firewall rules to ensure that SSH traffic is not being blocked.
Test with a standard SSH client to isolate the problem to Tabby or the device's SSH server.
Remember to always back up your configuration files before making any changes.

By following these steps, you should be able to diagnose and resolve the "Authentication rejected" error and successfully connect Tabby to your GL-iNet/OpenWRT device. If you're still having trouble, consult the Tabby documentation or seek help from the Tabby community.

For more information on SSH and its configuration, you can check out this SSH.COM Tutorial.