Skip to main content

Launch your FiveM server in just a few clicks! Optimized hosting, DDoS protection included, and 24/7 support.

Discover our FiveM plans

txAdmin troubleshooting

To install txAdmin, see Enable and configure txAdmin. To start from scratch, see Reset txAdmin.

The server starts an empty configuration (mapmanager, hardcap…)​

Symptom: the console shows the default resources (mapmanager, basic-gamemode, fivem-map-hipster), looks for hardcap, detects only about twenty resources, and none of your resources (oxmysql, ESX, QBCore…) start.

Cause: txAdmin does not point to the folder containing your server.cfg and your resources/ folder.

Fix, without touching your files:

  1. Open txAdmin → left menu Settings → FXServer tab.
  2. Server Data Folder: /home/container (the folder containing resources/ and server.cfg).
  3. CFG File Path: server.cfg.
  4. Click Save, then restart the server.

On the next start, the console should list many more resources, including yours.

hardcap​

hardcap is built into FiveM: do not add it by hand. If the console says it cannot be found, the path configured in txAdmin is wrong (see above).

The txAdmin page does not open (ERR_CONNECTION_RESET)​

txAdmin listens on a dedicated port, in the 40000 - 40200 range, set by the panel in the Startup variables. Its exact address is shown in the console at startup:

All ready! Please access:
http://IP:40xxx/

If you changed this port (for example to the game port), the page becomes unreachable: put back the txAdmin port shown in the panel's Network tab, restart, then use the address shown in the console.

"Access denied" in game on the admin menu​

Your txAdmin account is not linked to your player identifiers:

  1. Make sure you are logged in to your cfx.re account in FiveM, then join your server.
  2. In the txAdmin web interface, open Players, click your player, then the IDs tab.
  3. Open Admin Manager, edit your admin account and add the identifiers shown (fivem, discord, license).
  4. Save, then reconnect in game.

"Awaiting scripts"​

This error comes from the framework or your configuration (resources), not from the hosting: see Awaiting scripts.