txAdmin in Agora: sanctions, whitelist requests and the relayed interface

In short. If your game server runs under txAdmin (version 8 or newer), the agora resource detects it by itself and Agora draws three things from it: sanctions on the member's record, whitelist requests next to applications, and the full txAdmin interface in the Server → txAdmin tab. Without txAdmin, none of this shows up and nothing costs anything.

What the resource reports #

The resource listens to txAdmin events (warning, kick, ban, revocation, whitelist request, announced restart) and sends them to Agora in batches, without polling the server. It never sends an IP address, a hardware ID or the text of a direct message.

• Administration → Members, member record: txAdmin sanctions (warning, kick, ban with reason, author, duration, revocation), next to the Agora suspension. The link is made through the player's license linked by code: see Link your game.
• Moderation → Applications: txAdmin whitelist requests (pending, approved, refused), with a link to the player's Agora application.
• Server → Console: a txAdmin box with versions, the next restart and the latest events.

Sanctions are kept; other events are purged after 90 days. This feed can be turned off in the tablet settings (Administration → Configuration → Agora resource).

The txAdmin tab #

Server → txAdmin shows txAdmin's full web interface (live console, players, bans, scheduled restarts, admins). It is not a copy: it is txAdmin itself, relayed by the Agora server.

Who gets in. Access follows the person's txAdmin account, not their Agora group:

You also need a session opened on the site (not from the game), an account that is not suspended, and staff 2FA. The link with txAdmin goes through the Discord account linked to the Agora account. Agora reads txAdmin's admin list from its admins.json file (through the panel, otherwise SFTP) and keeps no password or token. The Reload txAdmin accounts button refreshes the list; if the file stays unreadable, only Agora administrators get in.

Signing in. In the frame, you sign in to txAdmin with your own account: your txAdmin permissions apply. Agora stores no txAdmin password. Every opening is noted in the administration log.

Set it up #

1. Open Server → txAdmin (administrator, 2FA).
2. Enter txAdmin's address as the Agora server reaches it (for example http://10.0.0.5:40120, no path or credentials). Agora suggests one from the panel.
3. Click Test.

The tab shows up as soon as txAdmin is detected or the address is set.

For isolation, the interface is served on a second Agora port, 40121 by default:

If the site is on HTTPS, the relay must be too, or the tab refuses to open. AGORA_TXADMIN_PORT=off turns the relay off. See Environment variables.

Limits to know #

• txAdmin rate-limits per IP address: from txAdmin's side, everyone comes from Agora, and its logs show Agora's IP, not the administrator's.
• Server restarts go through txAdmin: the panel console does not reach the game server under txAdmin. See also Edit server.cfg.