Skip to main content
This guide covers common issues encountered during installation and server operation, with step-by-step solutions.

Quick Diagnostics

Before diving into specific issues, run these quick checks:
1

Check Prerequisites Running

2

Verify Server Console

Look for the exact error message in server console - most errors are self-explanatory
3

Check F8 Console

In-game, press F8 to see client-side errors (JavaScript errors, network issues)
4

Review Logs

Check server logs for detailed error information

Installation Issues

Server Won’t Start

Error:
Solutions:
  1. Verify license key in server.cfg is correct
  2. Check key matches your server IP
  3. Generate new key if IP changed: Cfx.re Portal
  4. For localhost testing, use 127.0.0.1 as the IP when generating
Test:
Error:
Solutions:Windows:
Linux:
Error:
Solutions:
  1. Install Visual C++ Redistributables:
  2. Install .NET Framework 4.7.2 or higher
  3. Run as Administrator
Error:
Solutions:

Database Connection Issues

Error:
Solutions:Step 1: Verify MongoDB is Running
Step 2: Test Connection
Step 3: Check Connection String
  • Verify format in server.cfg:
  • Common mistakes:
    • Missing authSource=admin with authentication
    • Wrong username/password
    • Wrong port (default is 27017)
Step 4: Check Firewall
Step 5: Check MongoDB Logs
  • Windows: C:\Program Files\MongoDB\Server\6.0\log\mongod.log
  • Linux: /var/log/mongodb/mongod.log
Error:
Solutions:Issue: Wrong Credentials
Issue: Database Doesn’t Exist
Issue: Connection String Format Verify format:
Common mistakes:
  • Special characters in password not URL-encoded
  • Missing database name
  • Wrong port (default is 3306)
Issue: MySQL Not Running
Error:
Solutions:
  1. Increase timeout in connection string:
  2. Check database load:
  3. Restart databases:

Resource Loading Issues

Error:
Critical: mythic-base MUST start successfully. All other Mythic resources depend on it.Solutions:
  1. Verify folder exists:
  2. Check fxmanifest.lua exists:
  3. Review console for specific error:
    • Lua syntax errors
    • Missing files
    • Database connection issues
  4. Check Node.js installed:
  5. Try manual start:
Error:
Solutions:
  1. Check load order in configs/resources.cfg:
  2. Verify dependency exists:
    • Check if the dependency resource folder exists
    • Verify it’s not commented out in resources.cfg
  3. Restart in order:
Error:
  • HUD not showing
  • Inventory UI blank
  • Phone not appearing
Solutions:
  1. Check resource is started:
  2. Check for JavaScript errors:
    • In-game, press F8
    • Look for red JavaScript errors
    • Screenshot and analyze
  3. Clear FiveM cache:
  4. Verify UI build files exist:
  5. Check NUI devtools (F8 in-game):

Runtime Issues

Performance Problems

Symptoms:
  • Server FPS drops below 30
  • Player desync
  • Delayed interactions
Diagnosis:Press F8 in-game and type:
This shows which resources are using the most CPU and memory. Restart or optimize high-usage resources to improve performance.Additional Solutions:
  • Reduce player count if server can’t handle the load
  • Update resources to latest versions
  • Check system resources (Task Manager on Windows, htop on Linux)

Player Connection Issues

Error (Client):
Solutions:
  1. Verify server is running:
    • Check console shows “Server is ready”
    • No crash errors in console
  2. Check firewall:
  3. Check router port forwarding:
  4. Test connection:
  5. Check sv_maxclients not full:
Error:
Solutions:
  1. Check ban list:
  2. Check whitelist:
    • If queue/whitelist enabled, verify player is whitelisted
  3. Check anti-cheat:
    • mythic-pwnzor may be blocking player
    • Check console for anti-cheat messages
    • Temporarily disable to test: stop mythic-pwnzor
  4. Review connection logs:
    • Check Discord connection webhook
    • Look for specific rejection reason
Symptoms:
  • Stuck at character selection
  • Infinite loading
  • Spawn but can’t move
Solutions:
  1. Check mythic-characters started:
  2. Check database for character:
  3. Check F8 console (client):
    • Look for JavaScript errors
    • Network errors
    • Missing resources
  4. Try /logout command:
  5. Delete character cache:

Common Gameplay Issues

Solutions:
  1. Check keybind: Default is I
  2. Verify mythic-inventory started: status mythic-inventory
  3. F8 console - check for errors
  4. Try: restart mythic-inventory
  5. Clear cache and reconnect
Solutions:
  1. Verify mythic-hud started
  2. F8 console - check for JavaScript errors
  3. Try: restart mythic-hud
  4. Check if HUD is hidden: Some resources can hide HUD
  5. Clear FiveM cache
Solutions:
  1. Check keybind: Default is P
  2. Verify mythic-phone started
  3. Check if you have phone item in inventory
  4. F8 console - JavaScript errors
  5. Try: restart mythic-phone
Solutions:
  1. Verify mythic-commands started
  2. Check permissions (for admin commands)
  3. Verify syntax: /command arguments
  4. Check console for command errors
  5. Some commands require specific resources running

Advanced Troubleshooting

Enable Debug Mode

server.cfg

Check Logs

Server Logs:
  • Console output (save with logging software)
  • Discord webhooks (if configured)
  • Custom log files (if logging resource installed)
Database Logs:
  • MongoDB: /var/log/mongodb/mongod.log (Linux)
  • MySQL: Check error log location in MySQL config
FiveM Client Logs:
  • Windows: %localappdata%\FiveM\FiveM.app\logs
  • Look for CitizenFX_log_*.txt

Test Individual Resources

Network Diagnostics

Getting Help

If you can’t resolve the issue:
1

Gather Information

  • Exact error message
  • Server console output
  • F8 console output (screenshot)
  • server.cfg (remove sensitive data)
  • Steps to reproduce
2

Check Documentation

3

Community Support

  • Join Discord
  • Post in #support channel
  • Provide all info from Step 1
Before asking for help:
  • Try solutions in this guide
  • Search Discord for similar issues
  • Provide complete information (partial info = longer resolution time)

Prevention Best Practices

Regular Backups

Backup databases daily. Test restore procedures monthly.

Monitor Resources

Use resmon regularly. Watch for unusual CPU/RAM usage.

Update Carefully

Test updates on dev server before production. Always backup first.

Document Changes

Keep notes on configuration changes. Makes troubleshooting easier.
Most issues are configuration-related. Double-check server.cfg, database connections, and resource load order before assuming code issues.