Run txAdmin with Docker Compose

txAdmin ships inside FXServer. There is no official txAdmin-only Docker image that this guide can certify. Start from a reviewed FXServer container image or a Dockerfile you maintain with the correct Cfx artifact and runtime dependencies. Do not paste untrusted container images or example secrets into production.

Keep three things separateCopy Anchor Link

1. Artifact and process: the container must launch FXServer in txAdmin mode (not directly with +exec server.cfg).
2. Persistent storage: txData, deployed server.cfg / resources and any external SQL database must survive container replacement.
3. Networking: the txAdmin panel uses TCP, while the game server commonly needs both TCP and UDP on a separate port.

Compose patternCopy Anchor Link

The following is a configuration pattern, not a runnable certified FXServer image. Replace image name and container paths only after checking the entrypoint and volume layout of your chosen image.

services:
  fxserver:
    image: your-reviewed-fxserver-image:pin-a-version
    restart: unless-stopped
    environment:
      TXHOST_TXA_PORT: "40120"
      TXHOST_INTERFACE: "0.0.0.0"
      TXHOST_DATA_PATH: "/server/txData"
      TXHOST_FXS_PORT: "30120"
    ports:
      - "127.0.0.1:40120:40120/tcp"
      - "30120:30120/tcp"
      - "30120:30120/udp"
    volumes:
      - ./txData:/server/txData
      - ./server-data:/server/server-data

Important: A host-side 127.0.0.1 mapping restricts direct panel access on that host; it does not imply any restriction on the game ports. A container's TXHOST_INTERFACE=127.0.0.1 would instead prevent a host-to-container connection in many Docker bridge setups. The /server/server-data mount must match the image's actual deployment directory.

Bring it up safelyCopy Anchor Link

1. Ensure the reviewed image really contains compatible FXServer artifacts and that its entrypoint launches txAdmin.
2. Create storage directories owned by the container runtime user; check SELinux bind mounts on applicable hosts.
3. Start the container and inspect its logs for the txAdmin setup PIN and actual listening ports.
4. Use a private path or authenticated reverse proxy to access the panel. Keep the game ports reachable independently.
5. Complete first setup, run a recipe in the mounted server-data location, then connect a real test client.
6. Recreate the container once and confirm panel accounts, deployed files and player data persisted.

Failure casesCopy Anchor Link

• Only the container starts: inspect logs; game process may still need starting from txAdmin.
• Can't reach the panel: confirm published host mapping, firewall, and container listener.
• Missing files on restart: the volume mount might not match the image's actual txData or server directory.
• Database localhost failure: inside a container, localhost generally refers to the container itself, not a separate DB service.

See Environment & ports, backups, and Cloudflare Access for panel protection.

Sources: txAdmin environment reference, Docker port publishing.