FragNode Security Note: FiveM txAdmin & Rust Port Hardening
FragNode details a split-node security topology for public FiveM GTA RP and Rust servers so management panels, SQL sockets, and HTTP loading-screen assets never expose unprotected attack surfaces on the primary game node.
FragNode port-isolation rule: expose only the gameplay UDP/TCP port publicly; bind SQL and admin ports locally.
FragNode Published-Spec Summary
Even inline DDoS-filtered VDS instances suffer downtime when admins expose MariaDB (3306), txAdmin (40120), or Rust WebRCON (28016) to public scanners or serve multi-megabyte MP3/WebM loading screens directly from the game NIC. FragNode separates workloads by running gameplay binaries on a Dedicated VDS ($37.50/mo published 2026-11-12 UltaHost 32 GB tier) and offloading web portals and static loading media onto managed LiteSpeed web hosting ($2.95/mo intro on ChemiCloud).
FragNode Side-by-Side Published Architecture Matrix (2026-11-12)
| Technical Dimension | FragNode Split-Node Hardened Setup | Exposed Single-Box Configuration |
|---|---|---|
| Gameplay Port (30120 / 28015) | Allowed on Public Interface + Inline Scrubbing | Unfiltered Host Subject to IP Null-Routing |
| txAdmin (40120) & RCON (28016) | Blocked in UFW; Reached via SSH / WireGuard | Exposed to 0.0.0.0 Credential Stuffing |
| MariaDB / MySQL Socket (3306) | Bound Strictly to 127.0.0.1 Loopback | Open Externally to TCP SYN Exhaustion |
| Loading Screen Media & Guild Web | Offloaded to Separate Web Host + CDN | Served From Game VDS (Leaks Origin IP) |
| Linux Conntrack Tuning | Raised nf_conntrack_max + tcp_syncookies=1 | Default Table Drops New Player Handshakes |
FragNode source note: Published specifications and intro prices retrieved 2026-11-12 from official vendor documentation.
FragNode Implementation Decision Checklist
-
FragNode Architectural Guideline #1
Set bind-address = 127.0.0.1 inside /etc/mysql/mariadb.conf.d/50-server.cnf and restart MariaDB.
-
FragNode Architectural Guideline #2
Run sudo ufw default deny incoming, allow only your game UDP/TCP port plus key-only SSH, and tunnel txAdmin via ssh -L 40120:127.0.0.1:40120.
-
FragNode Architectural Guideline #3
Host loading-screen assets, forums, and donation webhooks on an external web account behind a CDN so HTTP floods never touch the game IP.
FragNode Architecture FAQ: FragNode Security Note: FiveM txAdmin & Rust Port Hardening
Why does FragNode insist on separating guild web hosting from the FiveM or Rust VDS?
Running WordPress or custom PHP scripts on the same IP as FXServer exposes your game machine to web-layer exploits and leaks the origin IP behind your domain.
How do co-admins open txAdmin if port 40120 is blocked by UFW in the FragNode guide?
Admins run a one-line SSH port forward or connect over a private WireGuard / Tailscale mesh IP, accessing txAdmin safely without exposing port 40120 to the public internet.