FiveM txAdmin Setup Guide 2025

txAdmin is the official web-based management panel for FiveM servers, providing complete control over your GTA V roleplay server through an intuitive interface. This guide covers installation, configuration, advanced features, and troubleshooting.

txAdmin Installation

Automatic Installation (Recommended)

txAdmin is included with FiveM server artifacts. After extracting FiveM files:

1. Windows: Run FXServer.exe to start the initial setup wizard
2. Linux: Run ./run.sh or ./FXServer to start setup
3. Follow the on-screen prompts to configure txAdmin
4. Create your master account (email and password)
5. Access txAdmin at http://your-server-ip:40120

Manual Configuration

If you need to manually configure or reconfigure txAdmin:

# Navigate to txAdmin directory
cd /path/to/fivem/server/txAdmin

# Windows: Edit config.json
# Linux: Edit config.json or use environment variables

# Config file location:
# Windows: C:\FiveMServer\txAdmin\data\config.json
# Linux: ~/fivemserver/server/txAdmin/data/config.json

Basic Configuration File

{
  "licenseKey": "YOUR_CFX_LICENSE_KEY",
  "serverName": "My FiveM Roleplay Server",
  "locale": "en",
  "masterAccount": {
    "email": "admin@example.com",
    "password": "hashed_password_here"
  },
  "webServer": {
    "port": 40120,
    "bind": "0.0.0.0"
  },
  "monitoring": {
    "enabled": true,
    "interval": 30
  },
  "backup": {
    "enabled": true,
    "frequency": "daily",
    "maxBackups": 7
  }
}

txAdmin Web Interface Setup

First Login Configuration

1. Access txAdmin at http://your-server-ip:40120
2. Login with your master account credentials
3. Complete the initial setup wizard:
   • Set server name and description
   • Configure server resources and scripts
   • Set up database connection (MySQL)
   • Configure server.cfg settings
4. Apply changes and restart server

Dashboard Overview

Advanced Configuration

Security Hardening

{
  "security": {
    "enable2FA": true,  // Two-factor authentication for master account
    "ipWhitelist": ["192.168.1.0/24", "10.0.0.0/8"],  // Restrict access
    "rateLimit": {
      "enabled": true,
      "maxRequests": 100,
      "windowMinutes": 5
    },
    "sessionTimeout": 3600,  // 1 hour session timeout
    "secureCookies": true  // Use secure cookies
  },
  "logging": {
    "level": "verbose",  // debug/info/warning/error
    "filePath": "/logs/txadmin.log",
    "maxSize": "100MB",
    "retentionDays": 30
  }
}

Database Integration

{
  "database": {
    "mysql": {
      "host": "localhost",
      "port": 3306,
      "user": "fivem_user",
      "password": "secure_password",
      "database": "fivem_server",
      "connectionLimit": 10
    },
    "redis": {  // Optional for caching
      "host": "localhost",
      "port": 6379,
      "password": "",
      "db": 0
    }
  }
}

Backup Configuration

{
  "backup": {
    "enabled": true,
    "schedule": "0 2 * * *",  // Daily at 2 AM (cron format)
    "retention": {
      "daily": 7,
      "weekly": 4,
      "monthly": 12
    },
    "include": [
      "resources/",
      "server.cfg",
      "txData/",
      "cache/"
    ],
    "exclude": [
      "*.log",
      "tmp/",
      "cache/unimportant/"
    ],
    "compression": "gzip",  // gzip/zip/none
    "storage": {
      "local": "/backups/fivem/",
      "remote": {  // Optional cloud backup
        "type": "s3",
        "bucket": "fivem-backups",
        "region": "us-east-1"
      }
    }
  }
}

Resource and Script Management

Managing Server Resources

1. Navigate to Resources tab in txAdmin
2. Upload resource files (.zip or extracted)
3. Configure resource settings and dependencies
4. Enable/disable resources as needed
5. Monitor resource performance and errors

Framework Integration

ESX Framework Setup

# In txAdmin Resources section
1. Upload ESX framework files
2. Configure database settings in es_extended/config.lua
3. Enable required resources:
   - es_extended
   - esx_menu_default
   - esx_menu_dialog
   - esx_menu_list
4. Configure jobs, items, and vehicles
5. Test framework functionality

QBCore Framework Setup

# In txAdmin Resources section  
1. Upload QBCore framework files
2. Run SQL scripts for database setup
3. Configure qb-core/shared/items.lua
4. Set up jobs in qb-core/shared/jobs.lua
5. Configure vehicles in qb-core/shared/vehicles.lua
6. Test core functionality

Monitoring and Performance

Performance Metrics

Metric	Normal Range	Warning Level	Action Required
CPU Usage	Below 70%	70-85%	Above 85% - Optimize scripts
RAM Usage	Below 80%	80-90%	Above 90% - Add RAM/optimize
Network In/Out	Stable	Spikes > 100MB/s	Check for DDoS/malicious traffic
Disk I/O	Low queue	Queue > 5	Upgrade to SSD/NVMe
Player Latency	< 100ms	100-200ms	> 200ms - Network issues

Alert Configuration

{
  "alerts": {
    "enabled": true,
    "notifications": {
      "discord": {
        "webhook": "https://discord.com/api/webhooks/...",
        "events": ["server_down", "high_cpu", "player_ban"]
      },
      "email": {
        "smtp": {
          "host": "smtp.gmail.com",
          "port": 587,
          "user": "alerts@example.com",
          "password": "app_specific_password"
        },
        "recipients": ["admin@example.com"]
      }
    },
    "triggers": {
      "server_down": {
        "enabled": true,
        "check_interval": 60
      },
      "high_cpu": {
        "enabled": true,
        "threshold": 85,
        "duration": 300
      },
      "high_memory": {
        "enabled": true,
        "threshold": 90,
        "duration": 300
      }
    }
  }
}

User Management and Permissions

Role-Based Access Control

Role	Permissions	Recommended For
Master Admin	Full access to all features	Server owner
Administrator	Server control, player management, backups	Head admins
Moderator	Player management (kick/warn), chat moderation	Game moderators
Developer	Resource management, configuration editing	Script developers
ViewerRead-only access to monitoring	Community managers

Permission Configuration

{
  "permissions": {
    "roles": {
      "master": ["*"],
      "admin": [
        "server.control",
        "player.manage",
        "backup.manage",
        "config.view"
      ],
      "moderator": [
        "player.kick",
        "player.warn", 
        "chat.moderate"
      ],
      "developer": [
        "resources.manage",
        "config.edit",
        "logs.view"
      ]
    },
    "users": [
      {
        "identifier": "steam:110000112345678",
        "role": "admin",
        "name": "Server Admin"
      },
      {
        "identifier": "discord:123456789012345678",
        "role": "moderator",
        "name": "Game Moderator"
      }
    ]
  }
}

Troubleshooting Common Issues

Best Practices

Security Recommendations

1. Use strong passwords: Minimum 12 characters with mix of types
2. Enable 2FA: Two-factor authentication for master account
3. IP whitelisting: Restrict access to trusted IP ranges
4. Regular updates: Keep txAdmin and FiveM updated
5. Separate environments: Use different instances for development/production
6. Audit logs: Regularly review access and action logs

Performance Optimization

1. Monitoring interval: Set to 60+ seconds for large servers
2. Database optimization: Regular maintenance and indexing
3. Resource management: Disable unused resources
4. Caching: Implement Redis for frequently accessed data
5. Backup strategy: Incremental backups for large servers

Integration with Other Tools

Discord Integration

{
  "integrations": {
    "discord": {
      "enabled": true,
      "botToken": "YOUR_DISCORD_BOT_TOKEN",
      "guildId": "YOUR_SERVER_ID",
      "channels": {
        "logs": "server-logs",
        "alerts": "admin-alerts",
        "chat": "game-chat"
      },
      "commands": {
        "status": "!status",
        "players": "!players",
        "restart": "!restart"
      }
    }
  }
}

External Monitoring

• Prometheus/Grafana: Advanced metrics collection and visualization
• UptimeRobot: External server monitoring
• Log aggregation: ELK stack or similar for centralized logging
• APM tools: Application performance monitoring

Migration and Backup

Server Migration Procedure

1. Full backup: Use txAdmin backup feature
2. Database export: MySQL dump of all databases
3. File transfer: Copy server directory to new host
4. Configuration update: Adjust IPs and paths in configs
5. Testing: Verify functionality on new server
6. DNS update: Point domain to new server IP

Disaster Recovery

# Disaster recovery script example
#!/bin/bash
# Restore from backup
BACKUP_DIR="/backups/fivem/latest/"
SERVER_DIR="/home/fivem/server/"

# Stop server
systemctl stop fivem

# Restore files
rsync -av $BACKUP_DIR/ $SERVER_DIR/

# Restore database
mysql -u fivem_user -p fivem_db < $BACKUP_DIR/database.sql

# Fix permissions
chown -R fivem:fivem $SERVER_DIR

# Start server
systemctl start fivem

Next Steps

• Set up MySQL database for FiveM
• Choose between ESX and QBCore frameworks
• Optimize FiveM server performance
• Configure server.cfg and resources
• Browse other game server guides