Skip to content

Troubleshooting

“No teammate can run yet: connect a model provider”

Section titled ““No teammate can run yet: connect a model provider””

hotline status says this on a fresh room. Connect a model, or give your teammates a harness that is already signed in for the hotline account.

“Pairing expired. Run hotline pair to try again.”

Section titled ““Pairing expired. Run hotline pair to try again.””

A pairing code lasts two minutes. Open the scanner on the phone first (Add a desktop), then run hotline pair.

  • Is the phone on a network that can reach the --public-url address? A server on a LAN address needs the phone on that LAN or your VPN.
  • Is the port open in the firewall?
  • Is the desk up? hotline status, then journalctl -u hotline.
Section titled ““Update the Hotline app to link to this server””

The phone is running a version from before servers. Update it from TestFlight.

“This phone is no longer paired with the desktop”

Section titled ““This phone is no longer paired with the desktop””

The server doesn’t know this phone any more: it was revoked, or the room was moved to a new store. Run hotline pair and scan again.

“The desk could not prove it is the desk you paired with”

Section titled ““The desk could not prove it is the desk you paired with””

Whatever answered at that address doesn’t hold the key from the QR code the phone scanned: a different machine, or a room recreated from scratch. If you rebuilt the server on purpose, pair again. If you didn’t, don’t.

A teammate’s harness can’t sign in or can’t be found

Section titled “A teammate’s harness can’t sign in or can’t be found”

The desk runs harnesses as the hotline account with the unit’s PATH. Check that Node (for npx) is on that PATH, and sign the harness in as the hotline account. See Connect a model.

serve refuses to start while the desktop app or another serve has the same room open. Stop the other one. Don’t delete desk.lock by hand.