williamnauroy/factorio-admin-rcon repository overview

⁠Factorio Admin RCON

Not a server manager: a hardened RCON admin console. Give moderators the server actions they need without handing them full RCON.

Documentation⁠ · GitHub⁠ · Security model⁠

• Three roles — viewer, moderator, administrator — enforced server-side: the action catalogue is filtered by role and execution re-checks the permission;
• bounded actions: the server builds the command from validated fields, so a moderator gets a "Kick" button without getting arbitrary Lua;
• audit log of every action, refusals included, in SQLite;
• raw RCON console, restricted to the administrator;
• metrics (CPU, memory, players, UPS) without mounting the Docker socket into the panel;
• English and French, inferred from the browser.

⁠Quick start

One directory, this docker-compose.yml, and a .env you generate. Nothing to clone.

services:
  factorio:
    container_name: factorio-server
    image: factoriotools/factorio:stable
    restart: unless-stopped
    ports:
      # Game port only. RCON stays unpublished: the panel reaches it over the
      # compose network, and the port hands full server control to whoever
      # holds the password.
      - "34197:34197/udp"
    volumes:
      - ./data:/factorio
    environment:
      - UPDATE_MODS_ON_START=true

  factorio-admin:
    container_name: factorio-admin-panel
    # A minor tag: patches arrive, a major never lands on you by surprise.
    # In production, pin the exact version instead.
    image: williamnauroy/factorio-admin-rcon:1.4-distroless
    restart: unless-stopped
    depends_on:
      - factorio
    ports:
      # Loopback only: the panel grants full RCON access.
      - "127.0.0.1:3010:3000"
      - "[::1]:3010:3000"
    volumes:
      # The directory, not the file: a regenerated rconpw is picked up as is.
      - ./data/config:/factorio-config:ro
      # Sessions, audit log and metric series (SQLite).
      - factorio-admin-data:/data
    read_only: true
    tmpfs:
      - /tmp:rw,noexec,nosuid,size=16m
    cap_drop:
      - ALL
    security_opt:
      - no-new-privileges:true
    mem_limit: 256m
    pids_limit: 128
    environment:
      - RCON_HOST=factorio
      - RCON_PORT=27015
      - RCON_PASSWORD_FILE=/factorio-config/rconpw
      - ADMIN_PASSWORD=${ADMIN_PASSWORD:?set it in .env}
      - SESSION_SECRET=${SESSION_SECRET:?set it in .env, 32 chars minimum}
      # No docker-socket-proxy in this stack, so the CPU and memory graphs are
      # off. Players and UPS keep working.
      - METRICS_DOCKER=false

volumes:
  factorio-admin-data:

Secrets are generated, not typed:

cat > .env <<EOF
ADMIN_PASSWORD=$(openssl rand -base64 18)
SESSION_SECRET=$(openssl rand -hex 32)
EOF

docker compose up -d
cat .env            # the password to log in with
                    # → http://127.0.0.1:3010

On the very first start the game server is still creating its map and data/config/rconpw does not exist yet — the panel reports RCON as unavailable for a few seconds and recovers on its own, without a restart.

⁠Essential configuration

The full reference⁠ covers the rest.

⁠Tags

Every release publishes four tags for each variant: the exact version, the minor, the major, and latest.

Both run as uid 1000 and are volume-compatible, so switching either way keeps an existing factorio-admin-data database. Pin an exact version in production.

Platforms: linux/amd64 and linux/arm64. Every release ships an SBOM and build provenance.

⁠Security

The panel binds to 127.0.0.1 by default and expects an HTTPS reverse proxy to be exposed — recipes for Caddy, Nginx, Traefik and Tailscale⁠.

What is in place: sessions persisted in SQLite so signing out really revokes the cookie, constant-time password comparison, login attempt limiting, per-session command rate limiting and a bounded RCON queue, origin checking on every mutating request, a nonce-based CSP, HSTS, a bounded request body, and an audit log that fingerprints rather than stores raw console commands. The panel holds no Docker socket.

Be clear about the limit: the admin role has full RCON access by design, which means arbitrary Lua. That is the account you protect, not one the panel can constrain.

Full detail: security model⁠ · SECURITY.md⁠

⁠Compatibility

Factorio 2.x including Space Age, any image exposing standard RCON, amd64 and arm64, Docker with the Compose v2 plugin. Not supported: Factorio before 2.0, non-standard RCON implementations, and running more than one instance of the panel against the same server.

⁠Support

Bug reports and questions: GitHub⁠. Include the panel version, your Factorio version, the deployment type and the output of /api/ready.

MIT licensed. Source: https://github.com/EdwinAlkins/factorio-admin-rcon⁠