txAdmin remote access: reach your panel securely from anywhere

Why does txAdmin only work on localhost:40120?

txAdmin listens on port 40120 by default, on the machine where FXServer runs. When you open localhost:40120 in a browser, localhost always points at the computer you are sitting in front of, not at your game server. That is why the address works perfectly while you are connected to the server itself (via RDP or a local install) and fails from your home PC: your browser is knocking on your own machine's port 40120, where nothing is listening. To access txAdmin from another computer you have to replace localhost with the server's real IP address or a domain that points to it, and make sure the port is actually reachable from the outside. Everything else in this guide is about doing that without leaving your admin panel, a tool that can restart the server and edit its config, wide open to the internet.

How to access txAdmin from another computer?

There are four realistic ways to access txAdmin from another computer, and they trade convenience against exposure. The direct route is opening or forwarding port 40120 so you can browse to http://your-server-ip:40120 from anywhere; it works, but it publishes your login page to the whole internet. A reverse proxy such as Caddy or Nginx adds HTTPS and lets you put extra locks, like an IP allowlist or basic auth, in front of the panel. A VPN or an SSH tunnel keeps the port completely closed to outsiders and is the safest option, at the cost of a small setup step every time you connect. Finally, Cloudflare Tunnel with Cloudflare Access gives you identity-based login with no open ports at all. Pick based on who needs access and how sensitive your server is; the sections below cover each option honestly.

Option 1: open or forward port 40120

Forward TCP port 40120 on your router or open it in your provider's firewall, then browse to http://your-server-ip:40120. This is the fastest way in, and also the most exposed: your txAdmin login page becomes visible to anyone scanning the internet, and bots scan for it constantly. From that point on, everything depends on password strength.

• Use a long, unique master password and unique passwords for every admin account. This is the bare minimum if the port is public.
• Never reuse passwords from your Discord, hosting panel or database.
• Changing the port number hides nothing from a scanner. Treat it as cosmetic, not as security.

Option 2: reverse proxy with HTTPS (Caddy or Nginx)

A reverse proxy sits in front of txAdmin: you point a subdomain such as panel.yourdomain.com at Caddy or Nginx, the proxy terminates HTTPS and forwards traffic internally to localhost:40120. You get encrypted logins plus a place to add protection layers that txAdmin does not ship with.

• IP allowlist: only your staff's IP addresses can even load the page.
• Basic auth in front: a second username and password before the txAdmin login appears.
• Port 40120 stays closed to the outside; only the proxy's HTTPS port is exposed.

Option 3: VPN or SSH tunnel

A VPN (WireGuard, Tailscale or similar) or a plain SSH tunnel keeps every panel port closed to the internet. With SSH you forward the port on demand: run ssh -L 40120:localhost:40120 user@your-server-ip and, while that session is open, http://localhost:40120 on your own PC reaches the panel on the server. Nothing is exposed publicly, which makes this the safest option; the tradeoff is friction, because every admin needs an SSH key or a VPN profile and one extra step before each session.

Option 4: Cloudflare Tunnel and Access

Cloudflare Tunnel runs a small cloudflared process on the server that opens an outbound connection to Cloudflare, so no inbound port needs to be open at all. Pair it with Cloudflare Access and the panel sits behind an identity check: staff authenticate with their email or SSO before Cloudflare ever forwards them to txAdmin. It is a strong middle ground: browser-only convenience like option 1, with exposure control close to option 3.

Can't access txAdmin? Common causes and fixes

If you can't access txAdmin from outside, the cause is almost always one of three things: a firewall, a hosting panel that maps ports, or the address txAdmin is bound to. Windows Firewall, ufw or your provider's security groups will silently drop traffic to port 40120 unless an inbound rule allows it. On managed FiveM hostings (Pterodactyl-style panels), txAdmin is often exposed on a different external port than 40120, so you must use the exact address and port shown in your hosting panel, not the default one. And if txAdmin was started bound to 127.0.0.1, it will only ever answer local requests, no matter what your firewall says. Work through those three in order, testing after each change, and you will usually find the blocker in minutes rather than hours.

• Test on the server first. If localhost:40120 fails there too, txAdmin is not running; the network is not your problem yet.
• Firewall rules: allow inbound TCP 40120 in the OS firewall and in your provider's security groups or control panel. Both layers must agree.
• Hosted servers: look for the txAdmin link or port mapping in your hosting panel and use that exact address.
• Bind address: if the panel only answers locally, check how txAdmin is launched and which interface it binds to.

Does your whole staff need txAdmin access?

Before you hand out txAdmin logins, ask what each staff member actually does. txAdmin can restart the server, edit the config, run console commands and manage bans, so every extra account is a real risk if it gets shared or phished. Most moderators only need to watch players and check their hours, and for that they do not need txAdmin at all. FiveMonitor is a web panel for FiveM staff that covers exactly that layer: live video of every player's screen, several players at once in the multi-player monitor, and playtime read from txAdmin's own playersDB.json. Each moderator gets their own sub-user account with a Discord login, so you never share a master password. Keep txAdmin restricted to the two or three people who genuinely operate the server, and give everyone else read-only eyes instead.

• Live screens from any browser: capture runs on each player's client, with 0% server FPS impact. See the live player monitoring guide.
• Player hours without panel access: playtime comes from txAdmin's playersDB.json; it needs the allow-fs-read flag, explained in the playtime tracking guide.
• Least privilege built in: sub-users with their own Discord logins, plus an API key you can restrict by IP.
• Honest scope: FiveMonitor is a monitoring and moderation panel, not an anticheat. It does not detect cheats or ban anyone; it complements whatever anticheat you run. Full details on the features page.

Set up safer access this week

If several people help you run your FiveM server, split access by role: keep txAdmin behind a VPN, an SSH tunnel or Cloudflare Access for the few who operate the server, and give moderators FiveMonitor sub-user accounts so they can watch screens and check hours from any browser without touching port 40120. Plans start at 9.99 EUR/month, with a 7-day free trial, no card required and cancellation at any time. Compare the available plans or create your account and start the free trial today.