Connecting to a Realm

Series: first-crossing · Part 3

Use the hostname and SSH port supplied by the operator:

ssh -i ~/.ssh/id_ed25519_archipelago -p 2222 [email protected]

The local source run uses 2222. The repository’s Docker Compose stack publishes 22022:

ssh -p 22022 traveler@localhost

First arrival

SSH asks you to verify the server host key. Confirm its fingerprint with the operator before accepting it.

A public key the realm has not seen starts registration. If invite gating is enabled, enter the token the operator gave you. Then choose the local name this realm will use for you.

The realm displays your did:key papers and opens its start room. Type:

> /help basics
> look
> smell
> listen

Return visits

The same public key resolves to the same account. Put the connection details in ~/.ssh/config:

Host winding-stair
  HostName realm.example
  Port 2222
  User traveler
  IdentityFile ~/.ssh/id_ed25519_archipelago

Then connect with ssh winding-stair.

If the connection is refused, verify the hostname, port, and operator status. “Beacon dark” is the fiction; TCP refusal still means no SSH listener answered.

Browser connection

No SSH client? Connect from your browser at /play. Enter the realm’s WebSocket address:

wss://realm.example/ws

The browser terminal renders the same ANSI interface as the SSH client. Session history persists within the browser tab. Refresh to reconnect if the signal drops.