FiveM Server Showing 0 Players — How to Fix It

A FiveM server showing "0 players" is a confusing problem — sometimes the server is genuinely empty and won't show on the list, and sometimes players are connected but the count reads zero. Here's how to diagnose and fix both.

First, identify which problem you have

There are two distinct "0 players" issues:

• Nobody can find or join your server (it doesn't appear, or shows 0/X and won't accept players)
• Players are connected but the count shows 0 (usually a OneSync or reporting issue)

They have different causes, so pin down which one you're facing before changing anything.

Cause 1: sv_maxclients not set correctly

If your sv_maxclients in server.cfg is missing, zero, or misconfigured, your server can refuse connections or misreport.

Fix: In server.cfg, confirm a sensible value:

sv_maxclients 48

It must be a positive number within FiveM's allowed range. Save and restart.

Cause 2: OneSync misconfiguration

OneSync changes how player state syncs. If it's off when your setup expects it on (or vice versa), player counts and visibility can break.

Fix: Make sure OneSync is set appropriately:

set onesync on

For most modern servers OneSync should be on. Our server.cfg guide covers this in detail.

Cause 3: Server not registered / license key issue

If your sv_licenseKey is missing or invalid, your server may run but fail to register properly with the server list, appearing empty or absent.

Fix: Get a valid key from the Cfx.re keymaster and set it in server.cfg. Watch the console on startup for licensing errors.

Cause 4: Endpoint / port problems

If your endpoint or port configuration is wrong, players can't connect and the server sits at 0.

Fix: Confirm your endpoint_add_tcp and endpoint_add_udp lines and that the port (default 30120) is open and forwarded. On a host, verify their networking setup. Connection-refused issues almost always trace here.

Cause 5: A crashed or hung resource

Sometimes the server process is alive but a broken resource prevents proper operation, so nobody can meaningfully join.

Fix: Read the console for errors on startup. If a resource is erroring, disable it and test. Our crash guide walks through isolating a bad resource.

Cause 6: Player count reads 0 but people are on

If players are actually connected but the count shows 0, this is usually a reporting/OneSync quirk or a script that queries player count incorrectly.

Fix: Verify OneSync is on and correctly set, update your artifacts to a current version, and check whether a specific resource is misreporting. Outdated server builds are a common culprit here.

The systematic approach

1. Read the server console on startup — licensing, endpoint, and resource errors show here.
2. Verify `sv_maxclients`, `onesync`, and `sv_licenseKey` in server.cfg.
3. Confirm your port is open and forwarded.
4. Update your artifacts if they're old.
5. Isolate resources if a crash is suspected.

Work through those in order and you'll find it — it's almost always config or networking.

Keep your server healthy

A lot of mysterious server issues trace back to poorly-built resources causing instability. Running clean, well-optimized scripts keeps your server predictable. At Viper Development, our scripts are built to run reliably and we offer real support if something misbehaves. Browse our scripts → or join our Discord.