txAdmin Troubleshooting
Check the first meaningful error in the FXServer console or txAdmin Live Console before changing configuration. A restart alone rarely fixes an invalid recipe, missing database or incorrect artifact.
txAdmin panel is not starting
Expected: Start FXServer with no +exec server.cfg argument to enter txAdmin monitor mode. The console then prints a panel URL and one-time setup PIN on first run.
# Linux example: run from the extracted server directory
cd /opt/fivem/server
./run.shIf the panel URL doesn’t appear, verify that you extracted a complete, recommended FXServer artifact for your platform and that the chosen port is available. By default, the panel uses TCP 40120.
Port already in use
Check who owns the game port (30120) or administration port (40120) before stopping anything:
sudo ss -lntup | grep -E ':30120|:40120'On Windows, use Get-NetTCPConnection and the process ID to identify the application.
Stop or reconfigure the known conflicting service gracefully; don’t immediately issue kill -9 against an arbitrary PID. If running two txAdmin instances, give each its own TXHOST_TXA_PORT, game endpoint and TXHOST_DATA_PATH (a separate txData folder), set as environment variables before FXServer starts. These replace the deprecated txAdminPort, txAdminInterface and txDataPath ConVars; see the txAdmin env-config reference .
Panel works locally, but not remotely
Prefer private access. On a Linux VPS, create an SSH tunnel:
ssh -L 40120:127.0.0.1:40120 YOUR_USER@YOUR_SERVER_IPVisit http://127.0.0.1:40120 on your computer. Confirm your SSH port is allowed and the tunnel remains connected. You do not need to open port 40120 to every public IP.
For players who cannot join, diagnose the separate game endpoint on port 30120 TCP and UDP, including host firewalls, provider rules and router NAT. See Networking.
Missing or invalid registration key
- Verify the server’s key in Cfx.re Portal → Registration Keys .
- Confirm it was supplied to the active txAdmin profile or the actual loaded
server.cfgassv_licenseKey. - Recheck the server-data path and logs for duplicate/placeholder keys.
Setting an arbitrary FIVEM_LICENSE_KEY environment variable by itself does not configure FXServer. Do not print your real key during debugging.
Recipe deployer fails
| Error | Check |
|---|---|
| Cannot connect to database | Database running; host, user, permissions and network reachability |
| GitHub download fails | Official repo URL, network access, temporary rate limiting and recipe revision |
| Permission denied | Ownership of the specific txAdmin data/resource directory |
| Resource fails to start | Missing dependency, fxmanifest.lua and first resource error |
| Duplicate or bad config | Selected active profile’s server.cfg and recipe-generated entries |
Do not re-run an install recipe over working production files as an attempted repair. Use a fresh staging profile or a verified restore.
If an update broke the server
Confirm the exact installed artifact build and revert to a previous tested version after stopping the process. Protect data and schema migrations with separate backups. See Artifact Update and Rollback, Server Backups and Common Errors.
Official references: txAdmin , Current setup wizard .