My FiveM server won’t start

A FiveM server that refuses to start almost always prints an explicit message in the txAdmin console. Solving it comes down to reading that log methodically.

Cause / The problem

Startup failures usually come from four sources: a missing or invalid license key (sv_licenseKey), a port that is unavailable or badly forwarded (30120 by default), outdated server artifacts, or a resource that crashes on load. The error message shown before the shutdown tells you which one.

Solution

1. Open the txAdmin console (Live Console tab) and find the last red line or the warning shown just before the shutdown.
2. Check the license key. If the message says “this server does not have a license key specified”, add to server.cfg: sv_licenseKey "your_key". Generate it on keymaster.cfx.re using the same Cfx.re account as the server.
3. Check the port. The “failed to bind to port” error means 30120 is already taken or blocked. Change endpoint_add_tcp / endpoint_add_udp or free up the port.
4. Update the artifacts. A build that is too old causes random crashes. Download the latest Linux or Windows version from the official Cfx.re website.
5. Isolate the resources. Comment out every ensure line in server.cfg, then restart. If the server starts, re-enable them one by one to find the one that crashes.
6. Check the dependencies (MySQL, oxmysql): an unreachable database prevents the ESX/QBCore frameworks from launching.

Once the cause is fixed, restart from txAdmin and watch the console until “server started” appears.