Skip to content

How to host for Remote seats

Your players live in three different towns, and each has Armarius on their own computer. They join your saga over the internet while it stays on yours.

The app on your computer listens to this computer only, on port 8790 unless you change it. Nothing on your network or the internet can reach it directly. A tunnel carries players to it. Players need the same major version of Armarius as you.

Hosting and inviting

  1. Add the players. Add each player on Saga Management's Players and say who plays whom, as in Before the first session. Their passcodes need at least 14 characters.
  2. Set up a tunnel. Choose one from Choosing a tunnel and point it at http://localhost:8790.
  3. Host. In Saga Management click Host for Players, choose Remote seats, and click Host. Give the Tunnel address, which Tunnel it is, and the Port (see Host for Remote Seats).
  4. Issue Invites. Issue Invite to each player and send it by chat or email (see Issue Invite).
  5. Check the words on the call. Each player pastes the Invite into Join a Saga on their title page or Sagas shelf, and checks your six words. They read you their device's three words.
  6. Approve. If the three words match your screen, Approve the device under Requests.
  7. Keep it running. Keep your computer awake and the tunnel running while people play.
  8. Stop. Click Stop Hosting in the Host for Players window. Closing the app asks first, as it ends every player's connection.

The players' side is in Join a Saga, and what they can expect of you in What a host can and can't see or do.

Choosing a tunnel

A tunnel is a small program on your computer that keeps one connection open to a company's servers, which give you an https address. Inside the tunnel the app runs its own encryption, locked to your host's key. The tunnel company carries what it can't read. It sees that someone connected, and when, but not what passed.

Choose one of these. The steps are as of November 2026, and each service changes its pages from time to time, so follow its own guide where these differ.

  • Cloudflare Tunnel (free, but you need a domain on Cloudflare). Install cloudflared, then cloudflared tunnel login, cloudflared tunnel create armarius, and cloudflared tunnel route dns armarius saga.example.com. In its config.yml, point the hostname at http://localhost:8790, then cloudflared tunnel run armarius, or install it as a service so it starts with Windows. In Host for Players choose Cloudflare Tunnel and the address https://saga.example.com. Where to go: developers.cloudflare.com, Cloudflare Tunnel. Its quick tunnels (trycloudflare.com) change address each time, so every Invite would be lost. Use a named tunnel.
  • Tailscale Funnel (free, and no domain needed). Install Tailscale and sign in. In the admin console's DNS page, turn on HTTPS and Funnel. Then tailscale funnel --bg 8790 publishes it at https://YOUR-PC.YOUR-TAILNET.ts.net. The public side must be port 443, 8443 or 10000, and the 8790 is your computer's. tailscale funnel 8790 off stops it. In Host for Players choose Another tunnel. Where to go: tailscale.com/docs, Tailscale Funnel.
  • ngrok (a free account gets one fixed address). Install ngrok, add your token, then ngrok http 8790 --url YOUR-NAME.ngrok-free.dev. A random address changes each time, so use your fixed one. Choose Another tunnel. Where to go: ngrok.com/docs.
  • A server you rent, a small one with a domain. On it, run a web server that adds https and passes the player's address on, such as Caddy (reverse_proxy localhost:8790). From your computer, open a reverse SSH tunnel to it: ssh -N -R 8790:localhost:8790 you@server. Choose Another tunnel.
  • Port forwarding on your router isn't offered. The app won't listen beyond this computer, and opening your router would show every player, and anyone who finds it, your home address. If you must, put a web server such as Caddy on this computer in front of it, as on a rented server above, and forward only port 443 to that.

Whichever you use, the address goes in Tunnel address (https://, nothing after the name), and the tunnel points at http://localhost:8790. The address isn't secret. The Invite carries it, always as a secure wss:// address, and a player's app refuses an Invite naming a plain ws:// one anywhere but on its own computer.

The app tells players apart by the address the tunnel passes on: Cloudflare's own header, or the last X-Forwarded-For entry, which ngrok and Caddy add. A tunnel that passes on none makes the limits count every player as one.

Remote seats: hosting safely

Issuing and revoking. Issue each player their own Invite, and send it a different way from your call if you can, such as a chat message or an email. It works once, on one device, for 24 hours. On the call, read all six of your words, and have the player check every one. Approve a device only when its player reads you the three words your screen shows.

A changed passcode, or one you reset, ends every seat still signed in with the old one at once. If a device is lost or a player leaves, Revoke its seat at once, under Seats. It's cut off within a second. A storyguide's device sees everything in the saga, so revoke it as soon as it's lost.

If you think your host key itself has leaked, say through a copy of your keychain, Rotate Host Key. Every Invite and seat ends, and everyone needs a new Invite and new six words. Seats nobody uses stop working after the days you set in Idle Expiry (90 unless you change it).

The Log, in Host for Players, records who did what and when. That covers Invites issued and redeemed, approvals and rejections, sign-ins and wrong passcodes, lock-outs and revokes. It also notes which records each seat read or changed, passcode changes and resets asked, role changes, and seasons advanced or undone by a storyguide. It never holds a passcode, a credential, an Invite's code or what was typed. It lives in your save folder, not in the saga, so players never receive it, and it keeps a year.

What the app does for you. A wrong passcode slows that device down, with three free tries and then growing waits, without locking anyone else out. A connection that floods, sends what the app doesn't understand, or stays silent too long is closed. Each player's seat receives only what that player may see, and every change they send is checked against what's theirs to change. The full list is in the app's threat model (docs/threat-model-remote-seats.md beside its source), and what the players are told is in What keeps you safe.

Hosting from a computer that's always on. Instead of this computer, a NAS, a small Linux computer or a rented server can host the saga for Remote seats day and night, with no window. See How to self-host a saga.

See also: How to host a saga for your troupe, Host for Players, Join a Saga, Players