Fix common FiveM server errors

Most FiveM server errors come from four things: the license key, a resource that won’t load, old server files, or a player’s game being on a different build. Find the message you see below, most common first. The Console shows the server’s side of each problem, and its crash helper suggests a fix when it recognises one.

Server errors

The server stops at the license key check

What you see: the Console shows an error about the server license key instead of Server license key authentication succeeded. Common wordings are no license key was specified, Could not authenticate server license key and An error occurred while checking server license key, sometimes with an HTTP code.

Why: the key is missing, mistyped, deactivated or regenerated, or Cfx.re’s key service didn’t answer.

Fix it:

1. Open portal.cfx.re/servers/registration-keys and check that the key is listed under Active.
2. Copy the key again from the Portal. If you regenerated it, the old one no longer works.
3. Paste it into the license key field in the panel and restart.
4. Open server.cfg. If it has a sv_licenseKey line, make sure it holds the same key, or remove the line.
5. If the message mentions HTTP 429, the key service is limiting requests. Wait a few minutes and start again, rather than restarting over and over.

The license key guide covers creating and regenerating keys.

Failed to start resource

What you see: the Console says a resource couldn’t be found or started, usually with its name.

Why: the name after ensure doesn’t match a folder in resources, or the folder isn’t a working resource.

Fix it:

1. Compare the ensure line with the folder name. They must match exactly, and are best kept lowercase. GitHub downloads often add -main to the folder name.
2. Open the folder. fxmanifest.lua must be right inside it, not one folder deeper.
3. Check the resource’s install guide for dependencies, and ensure those above it in server.cfg.
4. Type refresh in the Console, then ensure name to try again.

If no resources start at all and nobody can connect, server.cfg isn’t being loaded. Restore it from Backups or check that it’s still in the server’s main folder.

Error parsing script or Failed to load script

Why: Cfx.re says these usually mean the server files (artifacts) are too old for the script.

Fix it: update the server to the newest recommended build in Settings, then restart. If only one resource fails, it may also have a bug or need a newer framework version.

Server artifact version is outdated

What you see: players get a grey end-of-support (EOS) or red end-of-life (EOL) warning when they join.

Why: the server runs old server files. Cfx.re supports a recommended build until six weeks after the next one comes out, and builds more than three months old can’t be joined from the server list.

Fix it: update to the newest recommended build in Settings and restart. A grey warning still lets players in. A red one may not.

Failed to verify protected resource

What you see: Failed to verify protected resource and the resource’s name.

Why: an escrowed (locked) paid resource is missing files. Its .fxap file is hidden, and some upload tools skip hidden files.

Fix it:

1. In FileZilla, turn on Force showing hidden files in the Server menu.
2. Delete the resource’s folder on the server and upload the whole folder again.
3. Restart the server.

You lack the required entitlement to use a resource

What you see: You lack the required entitlement to use and the resource’s name.

Why: the escrowed resource was bought by a different Cfx.re account than the one that owns your license key.

Fix it: check that the license key in the panel belongs to the account that bought it, then restart. If you bought it on another account, transfer the asset to the key’s account on the Cfx.re Portal.

The server isn’t in the server list

Why: new servers can take up to 8 minutes to appear. A server is also missing or not joinable from the list if its key fails, its listing details aren’t filled in on the Portal, sv_master1 "" is active, its artifacts are too old, or it’s asleep.

Fix it: players can join by address with F8 in the meantime. Then work through the checklist.

Stuck at 48 players

Why: more than 48 slots needs an Element Club subscription (Argentum or higher) on the account that owns the license key. The subscription doesn’t change sv_maxclients for you.

Fix it: subscribe, wait up to 6 hours for the perk, raise sv_maxclients in server.cfg and restart. Over 64 players also needs set onesync on. See player slots.

The framework can’t reach its database

What you see: red database errors from oxmysql or a similar resource when the server starts, and players get stuck creating a character.

Why: the database settings in server.cfg (often set mysql_connection_string) point at the wrong place, or the framework’s tables were never created.

Fix it: check the connection line against your server’s database details. If you moved from another host, make sure it no longer points at the old host. If tables are missing, import the framework’s .sql file. Our team can help at support@wilderack.com.

Steam IDs are missing from players

Why: steam_webApiKey stopped working on November 4, 2026. Scripts, bans or admin lines that rely on steam: identifiers stop finding them.

Fix it: add set sv_enforceSteamAuth true to server.cfg and restart. Players then need Steam linked to their Cfx.re account. It needs server version 38004 or newer.

Player errors

Couldn’t load resource while joining

What you see: a player’s join stops with Couldn't load resource and a resource’s name, often with a download error after it.

Why: the player’s game couldn’t download that resource. It can be the player’s connection or antivirus, a very large streamed file, or a broken file on the server.

Fix it:

1. Ask the player to try again. Big first downloads sometimes fail once and work the second time.
2. If it fails for everyone, and always on the same resource, upload a fresh copy of it and restart the server.
3. If it fails for one player only, they can turn off their antivirus for a moment or try another network.

Client/Server game build revision mismatch

What you see: Connection rejected by server: Client/Server game build revision mismatch with build and revision numbers.

Why: the player’s FiveM and your server disagree about a GTA V build. It usually happens right after a GTA V update, and fixes itself once FiveM and server owners update.

Fix it:

• Owner: update to the newest recommended server build and restart.
• Player: in FiveM, select the gear icon, then Game, and pick the Update Channel that matches the server (Release for most servers). Restart FiveM.

The server turns a player away

What you see: a message such as “You’re not authorized to join this server”, or a request to join a Discord server first.

Why: an allowlist is on, or the player is banned. The exact text comes from txAdmin or a script on your server, so it varies.

Fix it: check txAdmin’s whitelist mode and the player’s ban status. In Discord modes, the player must link Discord to FiveM and be in your Discord server (with the right role, if you use one).

Can’t connect at all

If the join times out or is refused:

1. Check that Overview shows the server as Running.
2. Copy the address and port from the address card again. The port is not 30120 unless you have a Dedicated IP.
3. Check that endpoint_add_tcp and endpoint_add_udp in server.cfg use your server’s port.

Still stuck? Use Get help in the panel and tick the box to attach the console lines. A real person will reply.