Troubleshooting
Connection Issues
Why CtrlOps can't reach your server, and how to fix it in minutes.
You hit New Connection, fill in the form, click Connect SSH, and instead of landing in your server you see "Connection Failed" or "Taking longer than usual". This page walks through the most common causes and exact fixes.
What we'll cover
- Why a "Connection Failed" error appears and how to read it.
- Fixing wrong username, wrong key, or wrong IP.
- Firewall and security group fixes for AWS, GCP, Azure, DigitalOcean.
- What to do when CtrlOps says "Windows Server Not Supported".
- When to use the SSH Setup Wizard.
First, find the exact error
When a connection fails, CtrlOps shows the raw SSH error in the Connection Failed alert. The exact wording matters, scan the table below to find your case:
| What the error says | Most likely cause |
|---|---|
| "Connection timed out" | Firewall or security group blocking port 22 |
| "Connection refused" | SSH service isn't running on the server |
| "Permission denied (publickey, password)" | Wrong username, wrong password, or wrong key |
| "Host key verification failed" | Server's identity changed since you last connected |
| "Network unreachable" | DNS or routing problem |
| "Taking longer than usual" | Slow server, slow network, or wrong IP |
| "Windows Server Not Supported" | The server is running Windows; use a Linux server instead |
Common problems and fixes
When all else fails: gather details and ask
Before you reach out for help, collect:
| Info | Where to find it |
|---|---|
| Exact error from the Connection Failed alert | Copy directly from the modal |
| Server IP and username | The connection card on the Home page |
| Auth method | Password, .pem key, or SSH Agent |
| Cloud provider | AWS, GCP, DigitalOcean, etc. |
Output of ssh -vvv user@ip from your local terminal | Run on your local machine to capture verbose SSH logs |
Then bring it to:
- Discord community: discord.gg/hBmD2ZAf
- AI Assistant inside CtrlOps, paste the error and ask for a translation. It's surprisingly good at decoding SSH error messages.
Always keep a fallback way into your server, your cloud provider's web console, a second user, or a different SSH key on a different machine. The day your only SSH key stops working is not the day you want to be locked out.