Troubleshooting

Cannot sign in

Check the email, password, and verification code. Confirm that the device can reach the Aihper service. Do not delete local data as a first step, because it may contain work and key material.

The App cannot continue work

Confirm the target Desktop is online in Devices, then select it as the preferred Desktop. Remote start, steer, stop, and HITL delivery depend on the real-time presence connection.

A Node is offline

aihper info
aihper doctor

If it is signed out, run aihper login, pair, or join. If it is logged in but stopped, run aihper start. A remotely signed-out Node clears its local credential and does not reconnect until you authenticate it again.

Pairing or joining fails

One-time codes expire. Generate a new code and make sure you are using the right flow: Node pair is claimed by Desktop/App; Desktop creates the code used by Node join. A permanent short code is not interchangeable with either.

A key-protected action is blocked

Restore the correct data key from a trusted Desktop transfer or the 78-digit backup. Do not generate a replacement merely to dismiss the prompt: old ciphertext would remain locked.

Work stops for a decision

Open the pending human-in-the-loop item on Desktop or App. If it was already answered elsewhere, refresh the work state instead of submitting it again.

Credits are insufficient

Open the account balance in Desktop, review recent usage, and purchase an available credit pack if needed. A model round cannot begin when the required credit hold cannot be made.