OriginRouter AppApp troubleshooting
App troubleshooting
Classify the problem as an account, connectivity, device-trust, target-workspace, or CLI-runtime issue before taking corrective action. Repeatedly deleting devices is not a substitute for diagnosis.
When a diagnosis requires target-device commands, service logs, or effective-route checks, see CLI troubleshooting.
General check order
- Let the App finish account verification and confirm that it is not still loading.
- Run
originrouter doctoron the target computer. - Check
originrouter service status. - For local connectivity, inspect
originrouter local config show. - For cross-device connectivity, inspect
originrouter auth statusandoriginrouter remote status. - Confirm the selected target device in the App.
Common problems
| State | Check first |
|---|---|
| CLI unreachable | Service state, Local API address, port, and device key |
| Connected but request not delivered | Target online state, trust relationship, and bridge connection |
| Workspace unavailable | Whether the target CLI completed remote workspace authorize |
| Provider test failed | Base URL, authentication fields, real inference support, and proxy logs |
| Approval remains pending | Whether the target session is active and the CLI returned final acknowledgement |
| Operation unsupported by older CLI | Update the CLI and restart the service |
Collect diagnostics
originrouter --version
originrouter doctor
originrouter status
originrouter service status
originrouter auth status
originrouter remote status
Run these checks in order: confirm the version, run the full diagnostic, inspect installation and device state, confirm the service, check account authentication, and finally inspect remote connectivity.
If the background service does not start, inspect ~/.originrouter/logs/daemon.err.log and daemon.out.log. Remove credentials, tokens, sensitive workspace paths, and unredacted content before reporting an issue.