Console, panel and database explorer (Pro tier)

In short. The Server area (administrators) groups the machine and the game server: Console, Panel, Database, Players, .cfg editor, txAdmin. The panel, console and database explorer are Pro tier features.

Connect your panel (Server → Panel) #

1. In your panel, create a client API key: your account → API Credentials → Create API key, description "Agora". The key (ptlc_… or plcn_…) is shown only once.
2. In Agora, Server → Panel, Hosting panel (Pterodactyl / Pelican) block: paste the Panel URL and the API key (client), then Save.
3. Pick the FiveM server in the list, then Save.
4. Click Detect the configuration: Agora fills the resources folder, the server.cfg path, the MySQL credentials and the location of jobs.lua, and names the framework it found. If the framework is on Automatic (the default), it stays that way: the result says "“Automatic” setting kept". If it was fixed, detection updates it. If a different game database is already set in Server → Database, Agora does not overwrite it: it shows the database the panel found and waits for your confirmation (Replace the game database with the panel's button).

Security. The key gives access to every server of the account. Agora encrypts it in the database. Best practice: create a panel sub-user limited to files, console and power, and generate the key from that account.

Hosts with an in-house panel (ZAP, Nitrado, TCAdmin…) are not compatible: use the SFTP access to the FiveM server (no panel) block.

The game server console #

Server → Console shows the real state (CPU, memory, disk, uptime), the ▶ Start, ↻ Restart, ■ Stop buttons (and Force stop as a last resort), and a command field (refresh, ensure agora…).

A refused command (too many commands in a row, panel unreachable, expired session) keeps its message under the console until the next send, and the command goes back into the input box: nothing is lost silently. Console lines sent to Agora (error reports, with your consent) mask sv_tebexSecret, tebex_secret and mysql_connection_string like the other secrets, as well as Discord bot tokens, JWTs, Authorization: Bearer|Bot|Basic … headers and …_token= values.

As a precaution, gestures that act on the server are capped per administrator:

Beyond that, the "Too many gestures in a row on the server" message asks you to wait a minute; nothing is done.

The stream goes through the Agora server: your browser never reaches the Wings daemon. Nothing to open, nothing to set in allowed_origins, and the console works from a phone. The Agora machine only needs to reach the node.

If your daemon uses a self-signed certificate, paste its fingerprint into SHA-256 fingerprint of the daemon's certificate (optional). The refusal message shows the presented fingerprint: check it before pasting it.

SFTP access (without a compatible panel) #

Host, port (a number from 1 to 65535, 22 by default; any other value is refused when saving), user, password or private key, and the resources folder. Agora requires the host key fingerprint before sending your credentials: click Test the SFTP access, check the presented fingerprint, then Save this fingerprint.

The connection and the framework (Server → Database) #

At the top of the page, the Game database connection box sets the access to the game server's database: see Connect the game server database.

The Framework dropdown offers Automatic (recommended), the default on a new installation, then ESX, QBCore and QBox to fix it. Right under the dropdown, a status line says what Agora uses:

• "Detected: QBox (reported by the in-game resource)", or "… (from the database tables)": all good;
• "Not detected: …" followed by the reason: Agora does not guess, and the MDT reads no characters until it is sorted out. See Supported frameworks;
• "Fixed choice: no detection" when a framework is fixed;
• "Save to apply this choice" when you have just changed the dropdown.

An installation that already had a framework saved keeps it. To switch to Automatic: pick it, Save, then Test.

The database explorer (Server → Database) #

A phpMyAdmin-style explorer, on the same connection as the MDT: browse, filter, edit a row, see the structure, export as SQL or CSV, and an SQL console.

Safeguards: one statement at a time; any write requires ticking "Allow writing"; 1,000 rows at most; 30 seconds at most per query; emptying or dropping a table requires typing its name again. Every write goes to the administration log.

Exporting a table (SQL or CSV) is done as a stream: a big table is not loaded into memory, the download moves at your browser's pace and stops if you close the page. If the game database is unreachable during the export, you read a clear message written for the administrator (never the database's internal address or port). SQL errors from your own query (syntax, violated constraint) are shown as they are: that is the tool. The full export of the game database is described in Backups and restore.

Server → Players #

The Game server box shows players online, the framework reported by the resource, the resource version and the last signal received. It is the first place to look when the tablet does not work.