Troubleshooting
Host key changed
Mucq refuses to connect when a server's key changes. Here's how to tell a reinstall from an attack, and how to trust the new key.
On this page
devbox's host key has changed
Mucq didn't connect. The server now presents a key Mucq doesn't trust, and the card shows both fingerprints: the one it presents now, and the one Mucq trusts.
Why keys change
- The server was rebuilt. A reinstall, a new VPS from the same address, or regenerated host keys all give it new keys. Harmless.
- Someone is in between. A machine intercepting the connection presents its own key. Not harmless.
Mucq can't tell the two apart, which is why it doesn't offer to connect anyway. You can.
Check the new key
Look at the server's key from somewhere you trust: your provider's web console, or a session you already have open on the server.
ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub
If the card names an ECDSA key, read ssh_host_ecdsa_key.pub instead. Compare the SHA256: fingerprint with the new one on the card.
If you can't explain the change, or the fingerprints don't match, don't connect. Find out first.
Trust the new key
Once you know why it changed:
- Choose Edit Server… on the card.
- In Host Key, choose Forget Host Key… and confirm with Forget.
- Connect again. Mucq asks Connect to devbox? with the new fingerprint, as it did the first time. Check it once more and choose Connect.
Mucq trusts one key per host and port, so the new key applies to every server entry with that host and port.