RallyTone Web beta setup

Prepare a compatible LAN Server

The Server owner must supply a build that implements the optional WebTransport participant endpoint. Adding these variables to an older Docker image does not upgrade it. On that compatible build, enable the browser listener explicitly:

RALLYTONE_WEB_BIND=0.0.0.0:15383 \
RALLYTONE_WEB_ORIGINS=https://rallytone.bitinggoatsoft.win \
RALLYTONE_WEB_ADVERTISE_ADDRESS=192.168.1.10:15383 \
  ./rallytone-server

Replace 192.168.1.10 with the Server's reachable LAN address. RALLYTONE_WEB_ORIGINS must match the webpage's exact origin, without a path or trailing slash. Wildcard origins are not accepted. These settings take effect when the Server starts; its management page cannot change them.

Browser traffic uses UDP 15383; native party traffic continues to use UDP 15381. Allow the browser port only on the trusted LAN. The browser endpoint stays LAN-only even when native external access is enabled. Do not forward UDP 15383 from your router or expose management on TCP 15382.

Open HTTPS, verify, then join

1. Use a browser that supports WebTransport with certificate hashes, WebAssembly, AudioWorklet, and microphone access. The app checks these capabilities.
2. Obtain the invitation URL from the Server owner. Compare its endpoint and SHA-256 certificate identity through a separate trusted channel.
3. Open the invitation in RallyTone Web. It only fills the connection dialog: it does not trust the Server or join automatically.
4. Inspect the Server, confirm its identity, enter the party password if required, and explicitly join. Grant microphone access when your browser asks.

The browser endpoint has its own temporary certificate, valid for at most fourteen days. A Server restart changes that certificate and invitation; verify the replacement. This is separate from the persistent native Server identity. A participant pin does not replace the webpage's trusted HTTPS certificate.

Some browsers also require a separate Local Network Access permission for connections from this public HTTPS page to LAN devices. Grant it only if you trust this page and the verified Server. Managed policies may block access; use a supported native client or consult your administrator instead of disabling browser security checks. See the Chrome WebTransport permission notes ↗.

PWA, offline reopening, and limitations

Use your browser's install action where available. The app caches its static interface, WASM, and worklets—not party messages, audio, passwords, or invitations. Offline reopening displays the local interface; joining, chat, and voice still require a reachable Server. Loading this publicly hosted client for the first time requires internet access.

Background tabs stop voice, and losing focus releases held Push-to-Talk. The browser cannot host or discover LAN parties automatically, use global shortcuts or floating windows, import custom avatars, operate file attachments, or purchase/restore Store cosmetics. Native and browser features are not interchangeable.

Updates wait instead of reloading an active party. Close all pages and installed windows of RallyTone Web, then reopen them to activate a waiting update.