Runbook: Forge Disconnected
Trigger
Use this runbook when Laravel Forge shows one or more servers as disconnected.
Important Note
Forge disconnected does not always mean the production application is down. It may indicate Forge connectivity, SSH, agent, permission, or server management access issues.
Immediate Actions
| Step | Action | Owner | Evidence | Status |
|---|---|---|---|---|
| 1 | Check whether production services are actually impacted | Operations | Site/API health evidence | TBD |
| 2 | Record affected servers and IPs from Forge | Operations | Forge screenshot | TBD |
| 3 | Check whether Forge status affects deployments, user management, or monitoring | Operations | Impact note | TBD |
| 4 | Confirm whether the issue is related to Forge permissions, SSH, firewall, or agent status | DevOps / Technical Manager | Technical confirmation | TBD |
| 5 | Contact Laravel Forge support if dashboard connectivity remains unclear | Operations | Support ticket | TBD |
| 6 | Document final decision and production impact | Technical Manager | Decision record | TBD |
Classification
| Condition | Severity |
|---|---|
| Application is healthy and only Forge dashboard is disconnected | SEV-3 |
| Deployments or server access are blocked during active incident | SEV-2 |
| Production application is down | SEV-1 |
Evidence To Attach
- Forge disconnected screenshot.
- Server list and affected IPs.
- Production health check result.
- Technical manager decision.
- Forge support response if applicable.