Skip to content

Troubleshooting

Can't connect

What Mucq says when a connection fails, what it means, and what to do about it.

On this page

When Mucq can't connect, it says why in a sentence and, where it can, names the fix. Find the sentence below. Demo names stand in for yours: the server devbox, the user you.

The server can't be reached

Mucq couldn't reach devbox.example.com on port 22.

Nothing answered at that host and port. Check the Host and Port in Edit Server…, that the device is online, and that the server is up. From somewhere else, ssh you@devbox.example.com tells you whether the server answers at all. If the server is on a private network, the device has to be on it too: see Reaching your server.

While a server doesn't answer, its header reads Offline. Mucq keeps checking and reconnects by itself when it answers.

No local network access

Mucq can't reach devbox on your local network.

The server is on your local network, and Mucq hasn't been allowed there. On the Mac, allow Mucq in System Settings › Privacy & Security › Local Network; on iPhone and iPad, in Settings. Open Privacy Settings (on iPhone and iPad, Open Settings) takes you there, and Mucq connects as soon as it's allowed.

The key isn't accepted

devbox didn't accept the key

The server doesn't have this device's key in ~/.ssh/authorized_keys of the user Mucq logs in as. Choose Copy Install Command on the card, run it in a shell on the server, then reconnect.

Each device has its own key: a key added from your Mac doesn't let your iPhone in.

The password isn't accepted

Not logged in

The server refused the password. Choose Log In and enter it again. After three refusals in a row, Mucq stops and waits for you.

A kind of login Mucq doesn't support

devbox needs a kind of login Mucq doesn't support

The server doesn't accept the way Mucq logs in to it, by key or by password. It may only offer keyboard-interactive logins, which Mucq can't use. Turn on PubkeyAuthentication or PasswordAuthentication in the server's sshd_config. Keys are the better choice.

No SSH algorithms in common

Mucq and devbox have no SSH algorithms in common.

The server has no Ed25519 or ECDSA host key, or doesn't offer AES-GCM encryption. sudo ssh-keygen -A on the server creates the missing host keys; OpenSSH offers AES-GCM unless its configuration turns it off. See SSH support.

The server refuses the session

devbox refused another session (MaxSessions).

The server limits sessions per connection, and Mucq has reached it. Close a project on that server, or raise MaxSessions in its sshd_config.

devbox refused the session

The server let Mucq log in but not open a terminal. Check ForceCommand and PermitTTY in its sshd_config, then reconnect.

The connection drops

Connection lost

The link dropped, or Mucq couldn't reach the server. The session on the server is untouched. Choose Reconnect (⌘R). If the server is offline, Mucq says Waiting for devbox instead and reconnects by itself once it answers.

Still stuck

Show Log, in the Help menu on the Mac and in Settings › Help on iPhone and iPad, opens Mucq's log. Then write to us from the Support page.