Troubleshooting
On this page
Before changing settings
Preserve unsaved work. Record the app version, package source, operating system, CPU architecture, time and original error. Change one understandable factor at a time. Never clear configuration or disable TLS verification as a trial fix.
Follow the symptom
| Symptom | Check in order | Verify the result |
|---|---|---|
| App will not start | OS and architecture, complete extraction, publisher, system error | App starts and existing data remains available. |
| SSH timeout | Host/port, VPN, routing, network egress, proxy, server listener | A new shell responds on the intended host. |
| SSH authentication fails | Username, selected credential, private-key path/passphrase, server permissions | Identity is confirmed after login; avoid repeated lockout attempts. |
| Host fingerprint changed | Stop; verify independently with the administrator | Resume only after trusted verification. |
| SFTP transfer fails | Proxy limits, both paths, permissions, space, name conflicts | Small upload/download round trip matches. |
| Save fails | Keep editor open, check space/permissions, export a copy | Reopen and compare the saved document. |
| Preview fails | File type, static/run mode, resource paths, package components | A trusted small sample opens correctly. |
Reconnect carefully
A recovered connection starts a new shell. Confirm each target and split; verify any earlier remote job separately. A cancelled transfer may have left a partial file. Do not overwrite it without checking its state.
Collect a useful report
- Reproduce with a harmless sample if possible.
- Include the version and package source, OS/architecture, time/timezone, steps, expected and actual results, and exact error code.
- State whether the issue affects one or all connections/files, and whether unsaved work or partial transfers remain.
- Attach only relevant, redacted screenshots or log excerpts. Do not send a whole configuration directory, credential store, private key or token.
- Contact yzmeng1688@gmail.com. Response times are not specified.
Common questions
Missing menus may depend on version, platform, account permissions, active object or components. Kubernetes 401 means authentication needs checking; 403 means permissions need checking. Neither should be bypassed by weakening transport security. For AI/iChat failures, check the configured service, account and permissions before retrying a request.