Start with Connection Details
Check the app version, selected host, account and route. Open Connection Details from the disconnected or error badge. Try one relevant change at a time so you can tell what helped. Avoid repeatedly typing commands into a disconnected terminal.
Match the symptom to the next check
| Symptom | What to check next |
|---|---|
| New or changed server fingerprint | Verify independently with the administrator. Do not accept it merely to clear the error. |
| Authentication rejected | Check the username, selected key or password, passphrase and server-side permission. A relay login is a separate check. |
| Managed relay access denied | Confirm completed account sign-in and the service's current policy or allowance. |
| Custom relay reachable but no session | Confirm compatible client and agent versions, agent availability and destination permission. Reachability alone is not a session test. |
| Requested transport unavailable | Check installed capability, provider support and use-case compatibility. Review fallback deliberately. |
| File transfer stopped | Inspect the transfer result and destination before retrying or overwriting. |
| Paste cannot read the clipboard | Review platform permission, then try keyboard paste or the attachment picker. |
| Cloud save failed | Treat durability as unknown; resolve the service error instead of assuming a silent local backup exists. |
| Browser reports Configuration unavailable | Ask the deployment operator to repair configuration. Do not substitute an untrusted endpoint. |
| Update check failed | Treat version status as unknown, not up to date. |
| Share or assistant revocation unconfirmed | Verify actual access state. A failed request is not a successful cutoff. |
Check the remote outcome before retrying
A network interruption does not establish whether a command completed. Inspect the remote machine through an authorized connection before repeating a deployment, deletion or other consequential action. A persistent shell or detached process may still be running.
Send a useful support report
Include the application version and build, operating system, selected protocol and route type, the action you attempted, and a redacted error message. State whether the problem repeats and whether another approved route behaves differently. Include a timestamp and time zone when useful.
Do not send passwords, private keys, vault archives, recovery codes, full invitation links or unredacted authentication logs. Review screenshots for terminal content and personal information. Contact OmniTerm support, or your service operator for deployment-specific configuration.
Related guides: server verification, relay setup and backup and recovery.