Before you start
You must administer the server and know its allocated public IP and game port. The examples 192.0.2.10:30120 are fictional; use your actual allocation, even when its port differs. Preserve the original configuration and never publish secrets.
Start with a direct connection from FiveM
Use the client F8 console to try the allocated destination. Record whether failure happens before connection, during downloads or after joining. If direct connection succeeds, investigate the listing separately. If it fails, first examine startup and the network paths.
Test from the client F8 console
connect 192.0.2.10:30120This uses FiveM rather than a browser or the txAdmin port. Success validates the path from your connection at that time; it does not establish that every network or the Cfx.re listing service can reach the server.
Compare info.json from outside the server network
Check the public endpoint from an authorized external connection. If you have system console access, compare with an appropriate local test. A local response alone does not prove public reachability.
Bounded read-only HTTP request
curl --connect-timeout 5 --max-time 10 -fsS http://192.0.2.10:30120/info.jsonFXServer JSON validates this HTTP/TCP request. A timeout means this test did not complete; it does not locate the fault by itself. This does not validate UDP traffic. A txAdmin page is not an equivalent result.
Separate private appearance from listing registration
Inspect server.cfg and settings managed by your panel or Cfx.re portal. Current documentation distinguishes sv_master1, which can disable the connect button and show a private state, from registration with the listing service. It is no longer a way to remove a server from the master list. Do not add it when absent.
Check startup and Cfx.re authentication errors without putting a license key in a public report. Naming and project settings evolve with the server version and portal. Do not overwrite a working configuration using an old generic template.
Check endpoints, NAT and proxies
A bind address such as 0.0.0.0 is not the public address players should use. Behind NAT, compare the advertised IP and port, TCP/UDP destinations and relevant logs. Only use sv_listingIpOverride or sv_listingHostOverride when a NAT or proxy actually requires them.
Where protection or a proxy separates connection HTTP from game traffic, inspect both paths. A web proxy does not automatically forward UDP. Give support the allocation and relevant times rather than disable protections globally or change routes at random.
Consider the listing service independently
After confirming startup, allow registration to update and check Cfx.re status or support announcements. An empty browser search at one instant does not establish a persistent outage. Avoid repeated restarts that reset the diagnostic context.
If direct joining works but listing does not, retain the external info.json result and exact error. If only one network’s players fail, record that distinction. A listing problem does not automatically explain every connection failure.
Prepare evidence someone else can reproduce
Record the time zone, FXServer version, last change, assigned IP/port, F8 result, external HTTP result and relevant log excerpts. State whether NAT or proxies are involved. Redact Cfx.re keys, txAdmin tokens, unnecessary private addresses and personal information.
The existing FiveM loading guide is relevant when connecting works but a resource subsequently stalls. For listing issues, repeat the same checks after one targeted correction, from the original network and another authorized connection.
For your situation
| Situation | Next check |
|---|---|
| F8 succeeds but the browser entry is missing | Review private status, registration, advertised destination and external info.json rather than assume the game is stopped. |
| info.json responds but F8 fails | HTTP is only part of the path; compare UDP, endpoints and the exact client error. |
| No external test succeeds | First check startup, allocation and listening state; review rules for the specific port with support. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.