Common FiveM Errors and Fixes

Find the first actionable error, not just the last line after several failed restarts. Distinguish server-side errors (FXServer/txAdmin Live Console) from client-side errors (FiveM F8 console).

Log locations depend on the active txAdmin profile and host deployment. On Windows, FiveM client logs may be found under %localappdata%\FiveM\FiveM.app\logs. Redact license keys, tokens and player identifiers before sharing logs.

Server fails to start

“This server does not have a license key specified”

FXServer has not loaded a valid sv_licenseKey.

1. Create/check the key at Cfx.re Portal → Server Registration Keys .
2. For a txAdmin recipe, paste the key in the active profile’s Recipe Deployer. For a manual server, add sv_licenseKey "YOUR_PRIVATE_KEY" to the server.cfg you actually load.
3. Verify the working directory and +exec server.cfg only if starting FXServer manually. For first-run txAdmin, start without +exec.

There is no requirement here to bind your registration key to a tutorial’s example IP address. Merely exporting FIVEM_LICENSE_KEY does not populate the native configuration variable.

“Address already in use”

Another service has bound your chosen game endpoint (usually 30120 TCP/UDP) or admin port (usually 40120 TCP).

sudo ss -lntup | grep -E ':30120|:40120'

Identify the owner and stop the correct service gracefully, or choose non-conflicting ports for a second server. Do not immediately kill an arbitrary PID with SIGKILL.

“You lack the required entitlement to use …”

Escrow-protected resources may require an entitlement owned by the Cfx.re account associated with the running server’s registration key.

1. Check the resource in the Cfx.re Portal  under the relevant assets/entitlements page.
2. Verify the server uses a registration key associated with the authorized account and the publisher has granted the correct entitlement.
3. Confirm the resource’s license/escrow compatibility with the target Legacy/Enhanced platform and restart after correcting the issue.

Do not attempt to bypass escrow. See Asset Escrow.

Players cannot connect

Server not showing in the server list or marked private

Start with Direct Connect from another network: in a FiveM client’s F8 console enter connect YOUR_PUBLIC_IP:30120, replacing the address and configured port. Record whether the player can join and spawn. A working txAdmin panel or a local loopback join does not establish external game connectivity.

The official server-issues guide  documents the listing checks. Do not make a Steam identifier mandatory or disable authentication as a speculative listing fix. Keep registration keys private; use Portal key setup and network-stage diagnosis.

Failed handshake / curl error 7

A curl error 7 indicates a failed connection to the endpoint named by that error. It does not identify one universal firewall, authentication or cache fix. Capture the full redacted error, timestamp and requested host/port. Determine whether it came from the client joining your server, FXServer contacting a platform service, or an individual resource contacting its own API.

For a game endpoint, check the listener locally, then attempt the same public endpoint from outside the host network. If HTTP works but joining fails, inspect the subsequent connection/UDP stage rather than declaring the server healthy. For a resource’s external API, check DNS, routing and the service listener from the FXServer host; changing the public game port may be unrelated. Follow the connection stages, compare both ends’ logs and test one correction at a time. A TLS/certificate error is a different failure from a refused TCP connection.

Do not publish private tokens or use curl -k as a generic repair. Success means the original failing action completes, not merely that a different URL returns 200.

Authentication session could not be established

• Restart FiveM and the game launcher, and check the client logs for the first error.
• Verify platform service status at Cfx.re Status  and the server’s outbound connectivity.
• Confirm the game server is actually running and 30120 TCP and UDP are reachable, not only the txAdmin web interface.

Steam/Discord identifier missing

The client might not have the relevant application running, or the server/resource assumes an identifier that not all clients provide.

• Check whether the specific resource requires Steam or Discord identification; do not assume Steam identifiers are always present.
• If required, sign in to the appropriate desktop application before starting FiveM.
• Use proper FiveM identifiers and a server-side identity/permission policy rather than turning off authentication to make a script work.

Loading or cache problems

First verify the server artifact track, required game build, active resources and a reproducible client error. Use the game’s built-in troubleshooting, client logs and official client support instructions.

Do not instruct users to blindly delete all cache or storage directories. These can contain additional data and might not be the cause.

Database errors (QBCore, ESX and similar)

ECONNREFUSED / access denied

1. Confirm your recipe actually requires a database (CFX Basic does not).
2. Verify MariaDB/MySQL service status and reachability from the FXServer host/container.
3. Check the active oxmysql mysql_connection_string and a dedicated application database user.
4. Test a credentialed database connection; check SQL error details without printing secrets.
5. Keep port 3306 private to the appropriate host/application network.

A current connection-string pattern is:

set mysql_connection_string "mysql://fivem_user:[email protected]:3306/fivem?charset=utf8mb4"

The example password is a placeholder. Do not use an empty-password/root-user connection string copied from an old XAMPP guide.

Missing table or column

Import the framework/recipe’s correct SQL schema and apply documented migrations after backing up data. Do not import an unrelated “latest” SQL dump into an existing production schema without review.

Resource and framework errors

“No such export …”

Check the target resource’s exact export name, supported version and start order. Confirm all declared dependencies started. Avoid guessing at legacy APIs.

ESX : Modern ESX uses supported imports/exports for shared objects. For a script from an older API generation, use the migration guidance from the exact ESX version; patching its manifest with an import shim is only appropriate where the upstream resource documents it.

QBCore : Scripts commonly use exports['qb-core']:GetCoreObject(), but compatibility depends on the installed core revision.

“Attempt to index a nil value”

Read the specific Lua file, line and stack trace. Potential causes include absent player state, missing resource initialization, invalid config, SQL query failures or a version mismatch. Add targeted checks and confirm expected data; don’t broadly patch unrelated files.

“Resource does not exist”

Verify the case-sensitive folder name, the configured server-data resources path, fxmanifest.lua and the corresponding ensure entry. Watch for an extra folder level after ZIP extraction.

1. Locate the active server-data directory for this txAdmin profile or manual launch. Do not put the resource only beside the FXServer binaries.
2. The expected shape is resources/[local]/my_resource/fxmanifest.lua, with scripts beside that manifest. my_resource/my_resource/fxmanifest.lua has an extra archive layer.
3. Confirm the file is not fxmanifest.lua.txt, its syntax is valid, and declared script paths/case match actual files.
4. In the server console run refresh, then ensure my_resource. Read the first error: “resource not found” differs from a manifest parse failure or missing dependency.
5. Start declared dependencies first. If the resource starts but an export is absent, check the provider version/API and resource lifecycle, rather than repeatedly renaming the folder.

Success means the resource starts and its documented client/server behavior works after reconnect or restart. Use the complete first resource as a known structure; source syntax checks cannot certify game-native execution.

Server thread hitch warnings

A hitch warning records delayed work in the reporting process; the message alone does not identify a faulty resource or justify a universal tuning preset. Distinguish startup-only warnings from a repeatable gameplay action. Save the warning time, artifact and resource revisions, player count and relevant host/SQL observations.

For recurring server hitches, record a server profiler record 500 capture around the action, then inspect and save it after recording completes. Compare like-for-like captures before and after one change. Use the full profiler procedure and performance triage. Client resmon measures that client’s resources; it is not a server hitch profiler. A slow query warning may correlate with a hitch without proving which caused the other.

Before reporting an issue

1. Reproduce it in a staging profile and capture the first error.
2. Record the server artifact build and Legacy or Enhanced platform.
3. Provide the relevant resource/framework versions, not just “latest.”
4. List what changed and what test failed.
5. Redact all passwords, registration keys, tokens, IP allowlists and personal data.

More guided checks: Troubleshooting Checklists, txAdmin Troubleshooting, FiveM Networking.