Article 5.8 - Common Error Reference
Short answerMatch symptom to likely cause and first fix. Each row links to deeper guides for SSH, web, disk, provisioning, Windows, and TLS issues.
Overview
Use this table for first-response triage on unmanaged VPS. Guest OS fixes are your responsibility unless scope says otherwise.
| Symptom | Likely cause | First fix |
|---|---|---|
| SSH: Connection refused | sshd down or wrong port | noVNC → systemctl start ssh — SSH refused guide |
| SSH: Permission denied | Wrong key/user | Verify -i key and username |
| 502 Bad Gateway | PHP-FPM/backend down | systemctl status php*-fpm — 502 guide |
| 503 Service Unavailable | App not running | Restart app; check listening port |
| Disk 100% full | Logs/data | Find large files — disk cleanup |
| OOM Killer | Insufficient RAM | Add swap or upgrade plan |
| Provisioning >10 min | Stalled task | Task History — provisioning guide |
| RDP timeout | Firewall 3389 | Windows Firewall rule — RDP guide |
| Certbot renewal failed | Port 80/DNS | UFW allow 80; verify A record |
Verify
- Original symptom cleared after fix
- Document command output if opening a ticket
Frequently Asked Questions
Error not listed?
Search the knowledge base by exact message text or open a ticket with full output.
Same as Article 5.6?
Article 5.6 is the unresponsive VPS flowchart; this table covers broader application and network symptoms.
Related Articles
Need More Help?
Search this knowledgebase for related guides. If the issue persists, open a ticket at billing.vpsgrid.net with your service ID, primary IP, and steps already tried. See What Information to Include in a Support Request and Security Responsibilities on Unmanaged VPS for scope and required details.
Was this answer helpful?
