Troubleshooting and support
When an error occurs, first check the account, server and project. Record the exact message and time.
Quick diagnosis
| Problem | Check |
|---|---|
| Server missing from the list | Account, direct sharing and team membership. |
| Missing control or denied access | Role, server state and ongoing operations. |
| Cannot read files or users | Server state, remote access and any busy-task message. |
| Git clone or pull fails | URL, branch, SSH permissions and local changes. |
| Script fails | First output error, runtime, directory, Linux user and environment. |
| Domain unavailable | DNS, active web server, its target and firewall. |
| Invalid HTTPS | Specific domain, mode, validity and certificate actually served. |
| Process not running | Applied configuration, command, port and process log. |
| Schedule did not run | Enabled state, frequency, timezone and latest operation. |
| Backup restoration unavailable | Stopped server, correct backup and completion of other operations. |
Unknown outcome
If connection was interrupted or an operation requires verification, establish the actual state first. Repeating a command can repeat data changes. Open the operation center, find the original task's details and use Verify status if available. For project tasks, use project history.
For security updates, the cloud verifies the outcome automatically and retries verification when the outcome is uncertain. No manual check or repeated installation is needed. Contact support if this state persists; see security updates.
Contact support
Use the application's help form when available. Check your contact email and describe the problem; messages must contain 3–1000 characters.
Include the server and project identification, time, last action, expected and actual result, and a short error excerpt. Do not send passwords, private keys, recovery codes or webhook secrets.