Troubleshooting

Common operator issues and direct next steps.

This page is for fast decision support. When in doubt, preserve logs first, then relaunch or recover with mirrored assets only.

Pin not detected

Check interposer seating, battery level, and the physical contact path first. If the browser path is not in use yet, fall back to the remote-auth shell workflow and verify the device still enumerates there.

Auth issues

If authorization fails, confirm the device prompt was accepted and use the isolated signer path only: https://pin.onenos.ai/api/pin/auth/sign.

Relaunch after reboot

Use relaunch when the install is still trusted and the daemon only needs to be restarted. If assets are missing or package state is unclear, switch to recovery.

Recovery flow

Recovery is the correct path when the daemon is gone, the primary app is unstable, or upstream dependency failure left the runtime in a bad state.

TLS / certificate issue

The hostname now has a dedicated certificate and isolated vhost. If you still see a cached browser warning, hard-refresh the browser or clear the remembered certificate state for this hostname.

Manual command fallback

Always pull commands from Install, Relaunch, Recovery, or Console. They are scoped to mirrored pin.onenos.ai assets only.