Academyacademy / hermes-101 / troubleshooting
Hermes 101 Troubleshooting
Support station - Recovery map. Use this whenever setup blocks you. Pass when you know the next smallest safe thing to try.
What this is
This is the recovery page for the Hermes 101 pilot path.
Why it matters
Server setup can fail for normal reasons: wrong IP, provider billing, missing credits, shell refresh, RAM limits, or command typos. A good workshop gives you a recovery map instead of making you feel stuck.
What to do
Use the smallest matching fix.
| Problem | Try this first |
|---|---|
| Cannot SSH | Check IP, username, server power, internet, and provider console |
hermes command not found | Run source ~/.bashrc, then try hermes --version |
| API key error | Check credits, full key copy, selected model, and provider status |
| Server slow | Run free -h, add swap, or ask before upgrading |
| Terminal fear | Copy one command at a time and read before pressing Enter |
| Not sure where commands are running | Check the prompt. Before SSH you are on your laptop; after root@...# you are on the VPS. Ask before running install commands. |
| Extra server created | Ask facilitator which server to destroy before leaving it running |
Command refresh:
Terminal command
source ~/.bashrc
hermes --version
hermes doctorDanger rule:
Reference
Do not run destructive commands such as rm -rf unless a facilitator explains exactly what they do and why they are safe.Common mistakes
- Rerunning setup without reading the error.
- Posting API keys in screenshots.
- Creating more paid resources while trying to fix one issue.
- Treating Telegram gateway failure as Hermes 101 failure.
Next step
Open the Command Sheet.