Reduced memory held per session and shortened the replay buffer window to 90 seconds.
Docs
What the gateway does, when the app uses it, and what to check when a session won't connect.
What the gateway does
The gateway relays session state between participants. It receives messages from each player and forwards them to the others, keeping scene changes, token positions and dice results in sync.
It does not store your campaign. Session state lives in memory for the duration of the session and is discarded when the last participant leaves.
When it is used
ZeroVTT opens a direct connection between browsers first. A table that connects directly never sends anything through the gateway.
The app switches to the gateway when the direct connection fails: strict NAT, a mobile network, a corporate firewall, or a browser that blocks peer-to-peer traffic. The switch is automatic and doesn't interrupt the session.
You can force a region in Settings, under Connection. The app remembers the choice per campaign.
Connection details
The gateway listens on TCP port 443 and speaks HTTPS with WebSocket upgrades. Nothing needs to be configured on the client side, and no extra port has to be opened.
| Region | Location | Status |
|---|---|---|
| eu-central | Frankfurt, DE | Operational |
| us-east | Ashburn, US | Operational |
| ap-southeast | Singapore, SG | Operational |
| sa-east | São Paulo, BR | Operational |
Hostnames for each region are assigned by the app and change with the routing table, so there is nothing stable to bookmark.
If a session won't connect
- Open the gateway page and run the connection check. If it fails, the address is blocked on your network.
- Corporate and school networks often block peer-to-peer traffic and long-lived WebSocket connections. Ask the network administrator, or use a different network.
- Extensions that block scripts or change user agents can break the WebSocket upgrade. Disable them for
zerovtt.comand try again. - If the check passes but the session still stalls, switch to another region in Settings. One region can be degraded while others are fine.
- Report a repeated failure through the app's Help menu. Include the time and your region so it can be matched against the logs.
Changelog
Faster region selection on mobile networks. Fixed a reconnect loop after a laptop woke from sleep.
Added sa-east. Health endpoint now reports the deployed version.
Moved the relay to a new connection handler. Sessions survive a gateway restart for up to 30 seconds.