Fix Connection Problems

Start with Test Connection in the host editor. Its result usually tells you whether the problem is the network, SSH authentication, or the selected transport.

Pairing does not complete

• Run mightty pair again and scan the new QR code. A code is valid for one pairing attempt.
• Allow camera access when Mightty asks for it.
• Keep the pairing command running until the app confirms the host was added.
• If pairing remains blocked, choose Add SSH Manually and use the same details as a working SSH client.

The host cannot be reached

Confirm the host name or IP address, SSH port, and username. The host must be awake, running an SSH server, and reachable from the network your mobile device is using.

For a private address, connect both devices to the same local network or VPN. Tailscale does not require a special Mightty integration: use the host’s Tailscale IP or MagicDNS name, make sure both devices are in the same tailnet, and verify that SSH is running on the host.

Authentication fails

Check that the selected method matches the host:

• A password must be the SSH account password, not a device unlock code.
• An SSH key must have its public half in the host’s ~/.ssh/authorized_keys.
• An encrypted private key needs the correct passphrase.

When manual key setup is uncertain, pairing can install a fresh Mightty public key without transferring the private key off your device.

The host fingerprint changed

Do not approve an unexpected fingerprint automatically. It can change after the host is rebuilt or its SSH keys are replaced, but it can also mean you are reaching the wrong machine.

Verify the new fingerprint on the host first. Only then use Settings → SSH Connection → Reset Trusted SSH Hosts and connect again.

Mosh falls back to SSH

Fallback is expected when the connection uses Auto and Mosh is unavailable. SSH remains a complete terminal connection.

To use Mosh, install mosh-server on the host and allow the configured UDP port range through its firewall or network. If SSH works but Mosh times out, UDP routing or firewall rules are the likely cause. Choose SSH explicitly when the network cannot support Mosh.

tmux is unavailable

Install tmux on the host, then reopen its destination list. Until then, choose Start Shell to connect without persistence. See Keep Your Work Running for installation commands and the difference between Mosh and tmux.

Still stuck?

Include the connection-test error, host operating system, selected transport, and whether another SSH client can connect when you contact Support. Never send a password or private key.