SSH & Domain Troubleshooting

Step-by-step resolution guide for SSH publickey permission errors, key agents, and .msrv.space hostname resolution.

Resolving `Permission denied (publickey)` Errors

If authentication is rejected when connecting via ssh -A <vm>@msrv.space:

Verify active keys in your local SSH agent:
```
microsrv:~$ ssh-add -l
```
If no identity is listed, add your private key to the agent:
```
microsrv:~$ ssh-add ~/.ssh/id_ed25519
```
Verify public key fingerprints: Confirm that the fingerprint of your local ~/.ssh/id_ed25519.pub matches the key registered under Console -> SSH Keys.

Resolving `Could not resolve hostname <vm>.msrv.space`

Ensure your target VM instance is in the Running state in the console dashboard.
Verify exact VM hostname spelling.
Flush local DNS cache if hostname resolution stalls:
- On Linux: sudo systemd-resolve --flush-caches
- On macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

← PreviousStateful OverlayFS & Persistent Storage Next →SSH Gateway & Secure Remote Access