Troubleshooting¶
Quick Fixes¶
Try these first.
Force Quit¶
If StormTunnel is frozen:
- Press Cmd+Option+Esc
- Select "StormTunnel"
- Click "Force Quit"
- Relaunch from Applications
Clear Known Hosts¶
If you see "Host key verification failed":
- Quit StormTunnel
- Delete
~/Library/Application Support/StormTunnel/SSH/known_hosts - Relaunch and reconnect (verify the new host key)
Reset StormTunnel¶
This deletes all settings and tunnels
Back up your configuration first using File > Export.
- Quit StormTunnel
- Delete
~/Library/Containers/in.rs.olujic.StormTunnel/ - Relaunch and reconfigure
Error Reference¶
Look up the error message you see:
| Error | Cause | Solution |
|---|---|---|
| "Permission denied (publickey)" | SSH key not authorized on server | Authentication Problems |
| "Connection timed out" | Network or server unreachable | Connection Timeout |
| "Connection refused" | Server not listening or SSH service down | Tunnel Won't Connect |
| "Port already in use" | Another app using the local port | Port already in use |
| "Host key verification failed" | Server key changed or unknown host | Clear Known Hosts |
| "Authentication failed" | Wrong password or expired credentials | Authentication failed (Password) |
| "Session Manager plugin not found" | AWS CLI plugin missing or not in PATH | Session Manager plugin not found |
| "Access Denied" (AWS) | IAM permissions insufficient | Access Denied or IAM errors |
| "Max retry attempts exceeded" | Persistent failure after all retries | Retry Exhausted Errors |
| "Port forwarding failed" | Remote service not available | Port forwarding failed |
Connection Issues¶
Tunnel Won't Connect¶
| Check | Solution |
|---|---|
| Hostname/IP correct? | Verify server address in tunnel settings |
| SSH port correct? | Usually 22, check with admin |
| Network connected? | Test internet connection |
| VPN required? | Connect to VPN first |
| Server accessible? | Ask admin to verify server is online |
Connection Timeout¶
- Increase timeout: Settings > General > Connection Timeout
- Check network: Try wired instead of WiFi
- Check firewall: Verify SSH port is not blocked
Tip
Use an IP address instead of a hostname to avoid slow DNS lookups.
Connection Drops¶
- Enable auto-reconnect: Edit tunnel > Advanced > Auto-Reconnect
- Check network stability: WiFi interference, cable issues
- Prevent Mac sleep: Adjust Energy Saver settings
Authentication Problems¶
"Permission denied (publickey)"¶
Your SSH key is not authorized on the server.
Warning
This is the most common connection error. Double-check which key file is selected in the tunnel settings.
- Verify correct key is selected in tunnel settings
- Ask admin to add your public key to the server's
~/.ssh/authorized_keys - Test manually:
ssh -i /path/to/key user@host - Try CLI fallback: Edit tunnel > Advanced > Use CLI Fallback
"Authentication failed" (Password)¶
- Verify password is correct (check Caps Lock)
- Re-enter password in tunnel settings
- Ask admin if password changed
- Try CLI fallback mode
Two-Factor Authentication¶
StormTunnel's native SSH does not support interactive 2FA prompts.
Workaround: Enable CLI Fallback mode:
- Edit tunnel > Advanced > Use CLI Fallback
- Connect -- you will see the 2FA prompt
- Enter your code when prompted
Port Issues¶
"Port already in use"¶
Another application is using that local port.
- Choose a different local port (e.g., 5433 instead of 5432)
- Find what is using the port:
lsof -i :PORT - Close the conflicting application
"Port forwarding failed"¶
- Verify remote host and port are correct
- Check if the service is running on the remote server
- Ask admin to verify the firewall allows the connection
AWS Session Manager Issues¶
"Session Manager plugin not found"¶
AWS CLI plugin is not installed or not in PATH.
- Install plugin:
brew install --cask session-manager-plugin - Verify in Settings > AWS > Plugin Status
- If custom location, set path in Settings > Advanced
"Access Denied" or IAM errors¶
- Check AWS profile is configured: Settings > AWS
- Verify IAM permissions with your AWS admin
- Test AWS CLI:
aws sts get-caller-identity
Required IAM Permissions¶
Your AWS admin needs to grant:
ssm:StartSessionssm:TerminateSessionec2:DescribeInstances(for instance list)
See AWS IAM Policies for full policy examples.
UI Issues¶
Application Won't Launch¶
- Check macOS version: Requires macOS 15.0+
- Check security: System Settings > Privacy > Allow StormTunnel
- Reset app: Delete
~/Library/Containers/in.rs.olujic.StormTunnel/and relaunch
Interface Frozen¶
- Force quit: Cmd+Option+Esc > Select StormTunnel > Force Quit
- Restart: Reopen from Applications
- Check resources: Close other apps if memory is low
Menu Bar Icon Missing¶
- Enable: Settings > General > Show in Menu Bar
- Check menu bar space (remove other icons if full)
- Restart StormTunnel
Performance Issues¶
Slow Connections¶
- Use IP address instead of hostname (avoids DNS lookup)
- Increase connection timeout
- Check network latency
High CPU/Memory¶
- Disconnect unused tunnels
- Restart StormTunnel
- Check Activity Monitor for other resource-heavy apps
Connection History Issues¶
History Not Showing¶
- Check privacy settings: Settings > Privacy > Connection History
- Verify tunnel is tracked (some tunnels can be excluded)
- Check license: Free tier limited to last 5 entries
- Restart StormTunnel
Missing Events¶
| Check | Solution |
|---|---|
| History tracking enabled? | Settings > Privacy > Enable Connection History |
| Tunnel excluded? | Check tunnel exclusion list in settings |
| Privacy mode active? | Host anonymization may affect display |
| App crashed during connection? | Events may be lost on crash |
Statistics Incorrect¶
- Verify date range: check the time period you are viewing
- Check for orphaned events: restart app to trigger cleanup
- Check filter settings: make sure filters are not hiding events
- Refresh view: Cmd+R
Performance with Large History¶
- Reduce retention: Settings > Privacy > History Retention Days
- Limit per tunnel: Settings > Privacy > Max Events Per Tunnel
- Clear old history
- Exclude frequently-changing tunnels from tracking
Search Issues¶
Search Not Finding Tunnels¶
| Problem | Solution |
|---|---|
| Typo in search | Check spelling, try partial match |
| Wrong field searched | Try different keywords |
| Tunnel recently deleted | Tunnel may have been removed |
| Search stuck | Clear search (Esc) and re-enter |
Search Performance¶
If search is slow:
- Archive old tunnels you no longer use
- Close other apps if memory is low
- Restart StormTunnel
Retry & Reliability Issues¶
Retry Not Working¶
| Check | Solution |
|---|---|
| Premium license active? | Retry is a Premium feature |
| Retry enabled on tunnel? | Edit tunnel > Advanced > Enable Auto-Retry |
| Connection errors? | Retry only triggers on connection failures |
| Retry count > 0? | Check max retry attempts setting |
Too Many Retry Attempts¶
- Lower retry count: Edit tunnel > Advanced > Max Retry Attempts
- Fix root cause: network issue, wrong credentials, server down
- Check logs: Connection History shows retry attempts
- Disable retry temporarily while debugging
Retry Exhausted Errors¶
| Possible Cause | Solution |
|---|---|
| Server down | Wait for server to come online |
| Wrong credentials | Verify SSH key or password |
| Network issue | Check VPN, WiFi, or internet connection |
| Firewall blocking | Verify SSH port is not blocked |
Tip
Check Connection History for error patterns. Repeated errors indicate configuration issues rather than transient failures.
When to Disable Retry¶
| Situation | Reason |
|---|---|
| Testing new configurations | Immediate feedback is better than retrying |
| Frequently changing credentials | Retries waste time with wrong credentials |
| Known server maintenance | Wait until maintenance is complete |
| Debugging connection issues | See each error individually |
Retry with Different Auth Methods¶
- Try CLI fallback: Edit tunnel > Advanced > Use CLI Fallback
- Check SSH key: verify key is in Settings > Keys
- Test password auth: temporarily switch to password method
- Update credentials: refresh password or key if expired
Warning
Passwords are not cached across app restarts. Retries may fail if the password was removed from Keychain.
Getting Help¶
Enable Debug Logging¶
- Settings > Advanced > Enable Debug Mode
- Enable Verbose SSH Output (for SSH issues)
- Reproduce the problem
- Check Console.app, filter by "StormTunnel"
Report an Issue¶
Include:
- StormTunnel version (Settings > About)
- macOS version
- Steps to reproduce
- Error messages
- Debug logs if available
Contact: support@storm-tunnel.app