Shared server and production

Server panel

Production administration in a browser: Discord sign-in, roles, console, players and bans, allowlist, restarts, backups, player data.

The panel is a page for running production that the agent sets up on your VPS. Moderators open it in a browser and sign in with Discord. They need neither the studio nor a Webexe Studio plan.

Turning it on

  1. In the studio open Shared server → Production.
  2. In Server panel click Turn on the panel. You can type a domain first.
  3. The studio registers the panel address on the account server, and the agent installs Caddy on the VPS and gets a Let’s Encrypt certificate for the IP address.

The panel runs at https://<VPS IP address>. It needs ports 80 and 443 free. If your own site with its own Caddy or nginx already runs on the VPS, the studio notices and says what to add to its configuration.

A domain of your own is optional: set an A record to the VPS IP at your domain provider and type the domain when turning the panel on. The studio checks that the record already points to the VPS.

Who can sign in

The studio team signs in with its roles (owner, administrator, dev). The owner adds other people by Discord ID in the studio or in the panel itself, on the Staff tab.

To copy a Discord ID in Discord: Settings → Advanced → Developer Mode, then right-click the person → Copy ID.

Role In the panel
owner everything, including adding people and moving from txAdmin
administrator console, start, stop and restart of production, players, allowlist, action log
moderator reads the console; players: message, warning, kick, ban and unban, notes, announcement
support players: message, warning, notes
dev reads the console

Roles that can type into the console, ban, back up or deploy (owner, administrator, moderator) sign in only with a Discord account that has two-factor authentication (2FA). Without it the panel refuses and says what to turn on.

Removing a person from the list works at once: their open session stops working on the next click.

Players

The Players tab in the panel and Players on production in the studio show who plays now: server number, ping, play time and the number of warnings. The agent adds the webexe_admin resource to production; it reports the players and carries out the panel’s actions.

  • Message goes to the player’s chat.
  • Warning covers their screen until they confirm it (the button works after 5 seconds).
  • Kick disconnects them with a reason.
  • Ban, permanent or for 24 hours, 3, 7 or 30 days, covers all the player’s identifiers (Rockstar license, Discord, Cfx.re account, Steam) and the hardware tokens of their computer. A new Rockstar account on the same computer does not get in either.
  • Unban in the player’s card lifts it at once.

Everyone who ever joined is in the search: by name or identifier (license:…, discord:…). The player’s card has the history of warnings and bans, staff notes, identifiers and recent sessions.

webexe_admin keeps the ban list and the allowlist itself, so it checks players while the agent restarts too.

Allowlist

With Let in only listed people and the staff on, the server lets in only identifiers on the list and the panel staff (by Discord ID). A refused player sees their identifier, which they can send to the staff.

Roles in the game

A panel role becomes an ACE group in the game: a moderator gets group.moderator on joining, support group.support, and so on. Resources that check IsPlayerAceAllowed see the staff without entries in server.cfg. You set what the groups may do in server.cfg, e.g. add_ace group.moderator command.kick allow.

Moving from txAdmin

The owner picks the file txData/<profile>/data/playersDB.json in the panel (Players tab) or in the studio. The panel moves players with their identifiers, hardware tokens, play time and notes, bans and warnings with their revocations, and the allowlist. Bans from txAdmin have IDs starting with TX-.

Operations

The Operations tab in the panel and Planned restarts in the studio.

  • Planned restarts at the times you pick (the VPS’s time). Players get warnings 30, 15, 10, 5, 4, 3, 2 and 1 minute before, and scripts get txAdmin events (scheduledRestart, serverShuttingDown) and save their data before the stop. You can skip the next restart and set a one-time one. An empty server can restart up to 30 minutes early.
  • Hangs. webexe_admin reports to the agent every 5 seconds. When it misses a minute, or the server does not answer HTTP for 3 minutes, the agent saves the last log lines to hang-<date>.log, starts the server again and sends an alert.
  • Last 24 hours: players, server tick, FXServer memory, machine load and memory, free disk space. Measurements stay for 30 days.
  • Alerts: crash, hang, failed deploy, failed backup, less than 5 GB of disk. They go to the action log and to a webhook, e.g. a Discord channel’s (Channel settings → Integrations → Webhooks). The owner sets the webhook in the panel.
  • Database backups: every night at 4:00 (seven nightly ones stay), before migrations, before every restore and on demand. A backup has the production database, panel.db and the running release. Restore stops the server, backs up the present state and restores the chosen one. The owner restores.

Player data

The server owner is the controller of their players’ data. The panel, webexe_admin and the backups run on their VPS. Webexe Studio has no access to this data; at a panel sign-in it only confirms the Discord ID of a staff member.

The panel keeps: identifiers, hardware tokens, names, play time, joins and leaves, warnings, bans and notes. The owner sets the retention periods on the Staff tab:

Data Default
joins and leaves 90 days
player with no visit and no active ban 12 months after the last visit
staff action log 12 months

The agent cleans up once a day. A player with an active ban stays until the ban ends.

A player’s data request: in the player’s card, Export data (JSON) saves everything the panel has about them. Delete player data deletes it; an active ban stays with its identifiers only and a noted basis, so it keeps working. The panel does not touch data in the game database (the framework’s characters and inventories): delete those in the production database.

Information for players: on the Staff tab the panel makes it from the retention periods, the server name and the owner’s contact, in Polish and English. Put it in the server rules or on Discord.

Action log

Every sign-in, refusal, change to the staff list, console command, player action, allowlist change, move from txAdmin, start, stop, restart, deploy and rollback of production goes to the log with its author and source (panel, studio, SSH). The owner and administrators see it: in the panel on the Action log tab, in the studio under Server panel.

When the account server is down

Discord sign-in goes through studio.webexe.pl. If that site does not answer, the owner signs in with a one-time link from SSH:

/opt/we-studio-agent/node/bin/node /opt/we-studio-agent/agent.mts panel-link

The link works once, for 15 minutes, and signs in as the owner.

Security

  • The account server returns a sign-in only to addresses your studio registered. A link with another return address does not work.
  • The sign-in confirmation is signed, valid for 60 seconds and works once.
  • A panel session lasts 8 hours.
  • The panel accepts changes only from its own page, so another site cannot send a command in your name.

A question this page does not answer? Ask it on Discord.

Webexe Studio

Click to see it at 100%.