Troubleshoot SSH Errors
Resolve common SSH connection errors (bad permissions, protocol banner, key auth) on Thunder Compute. Follow step-by-step fixes for tnr connect
issues.
Thunder Compute gives indie developers, researchers, and data-scientists low-cost cloud GPUs in a few clicks. Our CLI (tnr
) and VS Code extension wrap SSH setup, key management, and port-forwarding for you—see the Quick-Start guide for a full walkthrough.
When you run tnr connect
, the tool SSHs into your instance automatically. If something goes wrong, you might see errors such as:
- Bad permissions – “Try removing permissions for user: \OWNER RIGHTS (S-1-3-4) on file C:\Users<your_username>.ssh\config.”
- Error reading SSH protocol banner (often means the instance is out of memory and the SSH handshake cannot complete).
- Key authentication failed (your SSH key is outdated or misconfigured).
Follow the steps below to fix the problem.
1. Restart the Instance
A quick restart clears many transient issues:
Wait about a minute, then try tnr connect
again.
2. Test a Manual SSH Connection
Get a more detailed error message by bypassing tnr connect
:
3. Fix Common Issues
A. Out-of-Memory
If you see Error reading SSH protocol banner, the instance may have run out of RAM. Wait a few seconds and retry. For a permanent fix, launch an instance with more resources:
Tip: 16–32 vCPUs generally provide enough memory for most ML workloads.
B. Permissions Problems
C. Corrupted Known-Hosts or Thunder Compute Locks
Known-Hosts
Thunder Compute Locks & Keys
4. Reinstall the Thunder Compute CLI or VS Code Extension
If the steps above do not resolve the error, reinstalling the tooling often does:
- Remove the existing CLI or extension.
- Download the latest installer from Thunder Compute download.
- Re-run
tnr login
followed bytnr connect
.
5. Still Having Issues?
Open a ticket in our Discord support channel with the exact error output, and we will get you unblocked fast.
Happy troubleshooting!