Install txAdmin on Pterodactyl

txAdmin runs inside FXServer, not as a separate Pterodactyl application. Start with an egg that explicitly supports txAdmin; the community FiveM egg documents TXADMIN_ENABLED and the TXHOST_* settings. Egg variables and behavior vary between releases.

Before you startCopy Anchor Link

• Have a working Pterodactyl server, compatible FXServer artifacts, and a Cfx Portal license key.
• Allocate a game port (commonly 30120, TCP and UDP) and a separate panel TCP port (normally 40120). The egg may require additional allocations; use its documented defaults.
• Confirm the container has a persistent writable txData directory. Back up existing txData, server.cfg, resources, and any framework database before reinstallation.

Configure the eggCopy Anchor Link

1. In the Pterodactyl Startup tab, inspect the currently installed FiveM egg and its txAdmin switch. Where present, turn on TXADMIN_ENABLED=1.
2. Verify the panel-port allocation and set TXHOST_TXA_PORT to its assigned TCP port. Pterodactyl will not automatically expose an arbitrary container port merely because an environment variable names it.
3. Check whether the egg provides TXHOST_DATA_PATH; ensure it points to a writable persistent directory such as /home/container/txData.
4. Use TXHOST_GAME_NAME=fivem for FiveM or redm for RedM if the egg implements that option. Follow the egg's reinstallation requirements when switching games.
5. Inspect the final startup command. The txAdmin start must not pass +exec server.cfg; txAdmin handles deployment and launches the configured server itself.

Pterodactyl egg custom variables appear in the container environment, but they are not necessarily secrets. Do not save tokens in public egg definitions.

First bootCopy Anchor Link

1. Start the server from Pterodactyl. Read the Console for the txAdmin URL and temporary PIN.
2. Open the assigned panel address and link the appropriate Cfx.re account.
3. Deploy into an empty target folder and verify the server.cfg and resources directories.
4. Start the game server in txAdmin; running the container alone does not necessarily start the game.
5. Test both the panel login and a real client connection.

Diagnose the common failuresCopy Anchor Link

Security: A port allocation is not access control. Prefer limiting admin access at the network level; do not publish the panel as an unauthenticated public reverse proxy.

Sources: Pterodactyl game egg, Pterodactyl egg variables, txAdmin environment reference.