Uplance Monitor types FiveM
Monitor your FiveM server
Uplance asks your FiveM server the same question the server browser asks it, over its own dynamic.json endpoint on port 30120.
Free for 10 monitors · no credit card
The problem
The txAdmin dashboard says the server is running. The box answers pings. And your server has been missing from the browser for an hour, because the resource that crashed took the listener with it.
Players don't file tickets when they can't connect. They join someone else's server, and you find out when the population numbers come in the next morning.
What the check looks at
Reachable in the browser
Whether the server answers on its own HTTP endpoint at all, and how long the reply took.
Player count
Current clients against sv_maxclients, kept as history you can chart and publish.
Hostname
The hostname the server reports, with colour codes stripped — a broken start-up usually changes it first.
Map
The map name it reports, so a failed resource restart is visible rather than guessed at.
And the alert actually arrives
Most monitoring tools are fine until the one time the alert doesn't arrive. Uplance is built so that can't happen quietly.
- Every alert is written to an outbox before it is sent, and retried for about fifty minutes. A restart doesn't lose it.
- Once a week, a real test event is sent through every channel you've configured, and you're told which ones failed.
- If the alert pipeline is in trouble, the dashboard says so — it isn't buried in a log file.
- If the checker itself stops, the health endpoint returns 503 so an outside heartbeat can page you, and your status page says monitoring has stopped instead of showing stale green.
Common questions
- Which port does it check?
- Port 30120 unless you say otherwise, which is where FiveM serves dynamic.json. If you have moved it, give the port when you add the monitor.
- Does it need a plugin or an API key?
- No. dynamic.json is part of the server and is already public, so nothing is installed on your side and no token is stored.
- What if only one resource is broken, not the whole server?
- Call a heartbeat monitor from inside that resource. If the call stops arriving, the heartbeat goes down on its own while the server monitor stays green — so you can tell which of the two failed.
- Can my players see the status page?
- Yes, with 90-day uptime bars and live player counts per server. On paid plans it runs on your own domain, and your players can subscribe to it instead of asking in Discord.
Also monitored
Know it's down before your customers do.
10 monitors, 30 days of history, no credit card