Repository navigation
Troubleshooting
Solutions for common issues and error messages.
Symptoms: Install completes but no Hetzner Cloud icon in Activity Bar
Solutions:
-
Reload VS Code:
- Press
Ctrl+Shift+P(orCmd+Shift+Pon macOS) - Search for Developer: Reload Window
- Press Enter
- Press
-
Check VS Code Version:
- Open Help → About
- Ensure version is 1.85.0 or later
- If older, update VS Code
-
Reinstall Extension:
- Open Extensions (Ctrl+Shift+X)
- Search for "Hetzner"
- Click Uninstall
- Restart VS Code
- Reinstall from marketplace
Symptoms: Commands not found in Command Palette
Solutions:
-
Check if extension is active:
- Open Extensions (Ctrl+Shift+X)
- Click Hetzner Cloud Toolkit
- Verify it says Installed (not Install)
-
Check extension output:
- Open Output panel (View → Output)
- From dropdown, select Hetzner Cloud Toolkit
- Look for error messages
-
Try reload:
-
Ctrl+Shift+P→ Developer: Reload Window
-
Cause: Token is wrong, expired, or has insufficient permissions
Solutions:
-
Verify token format:
- Should start with numbers
- Should be 40+ characters long
- No spaces before/after
-
Check permissions in Hetzner Cloud Console:
- Log in to https://console.hetzner.cloud
- Project → Security → API Tokens
- Click your token
- Ensure Read and Write are both checked
-
Regenerate token:
- Delete old token from Hetzner console
- Create new token
- Update in extension (SETUP panel → Add Token)
-
Verify correct project:
- Make sure token belongs to the project you want to manage
- Don't use cross-project tokens (if applicable)
Symptoms: Token added but servers/networks list is empty
Solutions:
-
Wait for data to load:
- If you just added the token, wait 5-10 seconds
- Extension queries API in background
-
Check API token permissions:
- Go to Hetzner console
- Verify token has Read access to all resources
- Some tokens might be Deploy-only (insufficient)
-
Force refresh:
- Right-click SERVERS panel
- Choose Refresh (if available)
- Or reload:
Ctrl+Shift+P→ Developer: Reload Window
-
Check internet connection:
- Hetzner API might be unreachable
- Verify you can access https://api.hetzner.cloud in browser
-
Check firewall/proxy:
- Corporate firewall might block API access
- Try on different network (mobile hotspot) to test
- Contact IT if on corporate network
Cause: Token is missing or invalid
Solutions:
- Verify token still exists in SETUP panel
- If missing, add token again
- Regenerate token in Hetzner console if uncertain
Symptoms: Wizard is open but server creation seems stuck
Solutions:
-
Check network connection:
- Ensure internet is stable
- Try again after 30 seconds
-
Check server count limit:
- Hetzner trials have server limits
- Check https://console.hetzner.cloud for quota
-
Check firewall rules:
- Hetzner Cloud API might be blocked
- Try from different network
-
Cancel and retry:
- Close wizard (Escape key)
- Try creating again with simpler settings
Symptoms: Server created successfully but not showing in SERVERS panel
Solutions:
-
Wait 10-15 seconds:
- Extension polls API every 5 seconds
- New servers appear within one polling cycle
-
Force refresh:
- Right-click SERVERS panel
- If Refresh option exists, click it
- Or reload:
Ctrl+Shift+P→ Developer: Reload Window
-
Check in Hetzner console:
- Log in to https://console.hetzner.cloud
- Verify server exists in Cloud Console
- If it exists there, issue is with extension display
-
Check project:
- Ensure correct project is active
- Click project name in PROJECTS panel
- Verify token belongs to that project
Symptoms: Selected server type shows error or unusable
Solutions:
-
Check location:
- Not all server types available in all locations
- Try different location in Step 1
-
Check account limits:
- Trial accounts have restrictions
- Upgrade account or try smaller server type
-
Check API response:
- Open Debug Console (F12)
- Check for API error messages
Symptoms: Added key but not showing in SSH KEYS panel
Solutions:
-
Wait for sync:
- Wait 5-10 seconds for API sync
- Extension queries API every 5 seconds
-
Force refresh:
- Right-click SSH KEYS panel
- Choose Refresh (if available)
- Or reload extension
-
Check file permissions:
- Ensure
.pubfile is readable - Not corrupted or empty
- Ensure
-
Verify in Hetzner console:
- Log in to https://console.hetzner.cloud
- Project → SSH Keys
- Should appear there if successfully added
Symptoms: SSH connect fails with "Permission denied"
Solutions:
-
Verify SSH key is installed:
- Check local
~/.ssh/directory - Ensure private key exists (no passphrase required for root)
- Check local
-
Verify server has public key:
- Server was created with SSH key selected
- Check Hetzner console: Server → SSH Keys section
- Should show your key name
-
Check SSH daemon on server:
- Connect via root password:
ssh root@<server-public-ip> # (Use root password from server detail panel)
- Verify SSH is running:
sudo systemctl status ssh sudo systemctl restart ssh
- Connect via root password:
-
Fix permissions:
ssh root@<server-public-ip> chmod 700 ~/.ssh chmod 600 ~/.ssh/authorized_keys
-
Check .ssh/authorized_keys file:
cat ~/.ssh/authorized_keys # Should contain your public key
Symptoms: Ping between servers in same network fails
Solutions:
-
Verify both in same network:
- Check NETWORKS panel
- Both servers should be listed under same network
- Click each server to verify in detail panel
-
Check OS firewall:
ssh root@server1-public-ip # Ubuntu/Debian sudo ufw status sudo ufw allow from 10.0.0.0/24 sudo ufw reload # CentOS sudo firewall-cmd --list-all sudo firewall-cmd --add-source=10.0.0.0/24 sudo firewall-cmd --runtime-to-permanent
-
Verify private IPs:
ssh root@server-public-ip ip addr show # Should see 10.x.x.x or 172.x.x.x address -
Test connectivity:
# Get server2's private IP from detail panel ping 10.0.0.3 # Try more verbose ping -c 3 -v 10.0.0.3
Symptoms: Network disappeared from panel
Solutions:
-
Force refresh:
- Right-click NETWORKS panel
- Choose Refresh
- Or reload extension
-
Check Hetzner console:
- Log in to https://console.hetzner.cloud
- Networks section
- Is network still there?
-
Check for errors:
- Open Output → Hetzner Cloud Toolkit
- Look for error messages
Symptoms: VS Code UI sluggish when extension active
Solutions:
-
Disable status polling (if needed):
- Open Settings (Ctrl+,)
- Search
Hetzner - Look for polling interval setting
- Increase polling interval (default: 5 seconds)
-
Close unused panels:
- Fewer open panels = less UI redraws
- Close unused tree views
-
Reduce number of projects:
- More projects = more API calls
- Remove unused projects
-
Check system resources:
- Open Task Manager
- Check CPU/Memory usage
- Close other heavy applications
Symptoms: "Rate limit exceeded" error from API
Solutions:
-
Reduce polling frequency:
- Settings → Hetzner Cloud Toolkit
- Increase polling interval
- Default is 5 seconds (aggressive)
-
Limit concurrent projects:
- Keep only active projects configured
- Remove test/throwaway projects
-
Wait for rate limit reset:
- Hetzner Cloud limits: varies by plan
- Usually resets after 1 hour
- Check Hetzner console for limits
| Error | Meaning | Solution |
|---|---|---|
ENOTFOUND api.hetzner.cloud |
DNS lookup failed | Check internet, firewall, proxy |
401 Unauthorized |
Invalid API token | Regenerate token in Hetzner console |
403 Forbidden |
Token lacks permissions | Check Read & Write permissions |
404 Not Found |
Resource doesn't exist | Verify resource ID, refresh |
409 Conflict |
Resource in bad state | Wait, then retry |
429 Too Many Requests |
Rate limited | Reduce polling frequency |
500 Server Error |
Hetzner API issue | Check status page, try later |
- Check this page — Your issue might be listed
- Check Hetzner API Docs — https://docs.hetzner.cloud/
- Check GitHub Issues — https://github.com/brwinnov/vscode-hetzner-cloud/issues
-
Enable debug logging:
// settings.json { "Hetzner Cloud Toolkit.debug": true }
- Open GitHub Issues: https://github.com/brwinnov/vscode-hetzner-cloud/issues
- Click New Issue
- Include:
- VS Code version (Help → About)
- Extension version (Extensions → Hetzner)
- What you tried (steps to reproduce)
- What happened (actual error)
- What should happen (expected behavior)
- Screenshots/logs (if applicable)
**VS Code Version:** 1.85.2
**Extension Version:** 0.1.1
**Steps to Reproduce:**
1. Add Hetzner token
2. Open SERVERS panel
3. Click create server button
4. Fill in details and click Create
**Expected:** Server appears in sidebar after 10 seconds
**Actual:** No server appears, no error message shown
**Error Log:**
[Paste output from Output → Hetzner Cloud Toolkit]
**Screenshots:**
[Attach any relevant screenshots]Still stuck? Ask in GitHub Discussions: https://github.com/brwinnov/vscode-hetzner-cloud/discussions