Self-hosted server: session_revoked right after sign-in, phone app shows "reconnecting"

[paterskip]

Setup problem on a self-hosted server (not a form bug report). Filed as a question because the repository points setup questions to Discussions. Related closed issue: #5560 (closed by the bot because it was not created from a form).

Environment

• OpenBot 0.63.0 (self-hosted server installed with install-server.sh, --user openbotsrv --display-size 1600x900)
• Ubuntu 26.04.1 LTS, x86_64, 4 vCPU, 7.7 GB RAM, systemd
• Account: signed in via openbot login (email code). Account email is redacted here.

What happens

1. Server ran normally after install and was online.
2. At 16:00:50 the host received session_revoked and moved online -> error. Recovery did not run; the socket did not reconnect.
3. The service was restarted (16:03), then the host Signal loop began: repeated socket closes with codes 1006 and 1013, Host Signal move failed, it asks for a new home, and AuthApiError: The account service could not complete the request.
4. The service was restarted again (16:09). Signal errors stopped for a while, but no "host registered / online" log line appeared.
5. openbot logout and a fresh sudo openbot login (about 16:12). The new session was revoked within about one minute: session_revoked at 16:12:45, again online -> error.
6. The phone app (reinstalled, QR generated with openbot mobile-connect) shows "reconnecting" and never sees the server.

Relevant log excerpt (sanitized)

16:00:50 WARN [team-webrtc-host] Host Signal error session_revoked; the socket does not connect again.
16:00:50 WARN [host-service] Host phase online -> error: Signal recovery failed after error session_revoked.
16:07:19 INFO [team-webrtc-host] Host Signal socket closed with code 1006; it connects again.
16:07:34 INFO [team-webrtc-host] Host Signal socket closed with code 1013; it connects again.
16:07:39 WARN [team-webrtc-host] Host Signal socket is not ready after close 1013; it asks for a new home.
16:07:57 WARN [application-services] A server control request failed. AuthApiError: The account service could not complete the request.
16:08:15 WARN [team-webrtc-host] Host Signal move failed; the host tries again later.
16:12:45 WARN [team-webrtc-host] Host Signal error session_revoked; the socket does not connect again.
16:12:45 WARN [host-service] Host phase online -> error: Signal recovery failed after error session_revoked.

Other observations

• openbot status keeps printing Server: OpenBot (online) while the host phase in the log is error, so the CLI status does not reflect the signal state.
• Startup: Unable to register the openbot:// scheme (expected on headless) and MaxListenersExceededWarning: AgentService (11 listeners, limit 10).

Questions

• Why is a freshly issued host session revoked within a minute of sign-in?
• Does the account service revoke the previous host session when a new sign-in or phone pairing happens? If so, is there an expected way to pair a phone with a self-hosted server?
• Is AuthApiError at 16:07 a known account-service incident?

Steps to reproduce

1. Install with install-server.sh on Ubuntu 26.04, sign in with sudo openbot login.
2. Wait for the host to go online, then observe session_revoked (happened on the first run after about 25 minutes).
3. Sign out and sign in again; session_revoked recurs.