Category: Troubleshooting
- Server ID, project name, and recent action history are available.
- You can access activity logs or console in dashboard.
- You know the last successful state before issue started.
- Check server status and recent actions in dashboard activity history.
- Validate network path: IP assignment, security group, firewall, and open ports.
- Test access path by trying console and SSH independently.
- Review system logs for failed services or startup errors.
- If DNS-related, verify both forward and reverse records and propagation state.
- If issue follows change, restore from latest known-good snapshot.
- Escalate to support with timeline, server ID, and exact error output.
- Service endpoint responds and monitoring alerts clear.
- Access methods (SSH/console/dashboard actions) work consistently.
- No new critical errors appear in logs after corrective action.
- Changing multiple settings simultaneously and losing root cause traceability.
- Skipping log inspection and relying only on UI status indicators.
- Escalating without actionable diagnostics, increasing resolution time.