Translation out of date
The source content changed after this translation. See the Português version. View original
Common issues
What each status message means and how to resolve it.
Updated on Sep 16, 2026
Most issues are diagnosed with hinow-cli status and hinow-cli connect status. Here's what each situation means:
| Message | Cause | What to do |
|---|---|---|
offline · nothing is running the bridge | Nothing is running on this machine | Open the interface or run hinow-cli serve |
offline by choice | Someone ran connect offline | hinow-cli connect online |
another HiNow Code process ... holds its HINOW Connect link | The open interface holds the bridge | Use the **This machine** chip in it, or run --attach |
policy is 'ask' but only a headless server runs here | Headless machine with ask policy | hinow-cli connect allow (or serve --policy allow) |
no device called "x" is online | Wrong name or the machine is offline | hinow-cli connect devices shows the exact names |
not signed in | Not signed in on this machine | hinow-cli login |
revoked by the account owner | The machine was disconnected by the chat | hinow-cli connect online to reconnect |
| The remote session is not responding | The executor crashed, went offline, or the folder doesn't exist | Check journalctl -u hinow-serve there; verify the folder with the selector |
| The chat shows **Waiting for X to authorize this session…** | The machine is in ask: the request waits for someone at its interface | Respond to the request at the interface within 90 s, or run hinow-cli connect allow there |
| **X did not respond to the session request in time** | No one responded within 90 s, or the interface wasn't open on the machine | Open the interface there before sending the message, or set the machine to allow |
The login file is encrypted with the machine's identity; don't copy it from one machine to another. Run hinow-cli login on each one. The same applies to device identity: each machine has its own.
hinow-cli --print-logs --log-level DEBUG # logs na tela
tail -f ~/.local/share/hinow/hinow/connect.log # a ponte com o hub
journalctl -u hinow-serve -f # o serve como serviçoHiNow Code needs to reach server.hinow.ai (account), api.hinow.ai (models), connect.hinow.ai (hub, WebSocket on port 443), and downloads.hinow.ai (updates). Corporate proxies that block WebSocket break HINOW Connect; everything else keeps working.
Was this page helpful?