Connecting to a computer

Codes, unattended passwords, and when the host has to approve you.

Embed
Preview of the card
<a href="https://gaiadesk.net/docs/connecting"><img src="https://gaiadesk.net/docs/_api/public/orgs/89a5df38-be2c-4963-8823-21d4bd40a2ab/spaces/57b99ea0-d45a-4986-8aa6-6b0683c9fe1d/pages/acd465e6-d7fa-41e9-a62e-9d50136ebdbe/social-card.svg?v=3e7ae33eec8b" alt="Connecting to a computer" width="600" height="315"></a>

Every connection needs two things: the host's 9-digit address and a secret. The secret is either a one-time code or an unattended password, and which one you use decides whether the host has to approve you.

The connect form

The controller asks for two fields:

  • Address — the host's 9-digit ID.

  • Code or password — either the 6-digit session code or the host's unattended password.

You type whichever you have into the same field; the host figures out which one it is.

One-time code (host approves)

When you enter the 6-digit code, the host sees an approval prompt and has to click Allow before the session starts. Use this for ad-hoc help, when someone is sitting at the machine and can say yes.

The code is regenerated every session, so it's safe to share for a single connection and useless afterward.

Unattended password (no prompt)

When you enter the host's unattended password, the session starts with no prompt — nobody needs to be at the far end. This is what you want for your own always-on machines.

Set a password on the host under Settings → Unattended access. Anyone with the address and the password can connect, so choose a strong one — and consider an access allow-list to restrict who's even allowed to try.

If the connection is slow or drops

GaiaDesk connects peer-to-peer whenever it can. On strict corporate or carrier-grade networks it falls back to an encrypted TURN relay automatically. If a session is briefly interrupted, it shows a recovering… banner and re-establishes on its own rather than dropping you.

Updated