Evergreen troubleshooting guide. Official references checked on 16 September 2026. This is AI-assisted FiveMCoach editorial content, not an announcement or a report of a test on your server.
What should you record before changing anything?
Write down the public address and game port from your hosting panel, the server start time, and the exact symptom. “Missing in search,” “connect button unavailable,” and “connection times out” are different observations. Ask the reporter for the client edition they used and an exact error message. Keep credentials and player identifiers out of shared screenshots.
Create one incident note with three columns: test, result, next action. Assign one person to edit configuration while another repeats the same check. This is an editorial troubleshooting method: its purpose is to stop several people making conflicting changes.
Can an external player reach the server?
Cfx.re recommends testing Direct Connect from FiveM's F8 console with connect IP:Port. Substitute the actual public address and game port. From outside the server network, also open http://PUBLIC_IP:GAME_PORT/info.json; a JSON response is the expected HTTP result. The documentation explicitly distinguishes a public address from localhost. See Cfx.re server troubleshooting.
Record the connection result separately from the HTTP result. A successful web request is evidence about that request, not proof that every part of joining works. If you are unsure which address a provider exposes, ask the provider to identify the game endpoint before editing rules.
Which configuration deserves a closer look?
The official FXServer configuration example defines separate TCP and UDP endpoints. Compare those settings with the game port assigned by your host and its network rules. Do not paste a complete example configuration over a working server: it also contains unrelated startup, permission and license settings.
Use the configuration file referenced by the actual startup process. A file in an old backup folder is not evidence of current behavior. Save a copy before editing and note the exact line changed. For a managed host, use its supported configuration controls rather than making a competing copy.
For a public listing, check for an active sv_master1 "" line. The official example keeps it commented out, and the troubleshooting guide says not to add it if absent. Also check sets sv_projectName and sets sv_projectDesc. These listing settings appear in the official configuration reference.
Apply necessary changes during an agreed maintenance window. Have the external tester repeat the original test after the server is running again. If the symptom changes, record that as a new result instead of declaring the whole incident resolved.
What if joining works but the listing still does not?
Cfx.re notes that listing can lag behind startup and that the listing service itself can have problems. Avoid repeated restarts while investigating. Check the official service status page for a relevant incident and its timestamp; a historical incident is not evidence of a current outage.
Set a time for the next check and preserve the current working configuration. If the problem persists, give your host a compact report: start time and timezone, affected public endpoint, sanitized startup messages, external test results, and the one change already attempted. Ask a specific question, such as whether the configured game endpoint matches the host routing.
What counts as recovery?
For this incident, agree on two separate acceptance checks: a tester can join through the expected route, and a fresh search can locate the intended server listing. Record who checked and when. A result you cannot reproduce should remain marked as unconfirmed.
Once discovery works, continue with the server launch checklist. If multiple staff members need access during troubleshooting, use the txAdmin permissions review. For guided setup practice, explore the server-owner curriculum.
Verification limit: this guide was checked against the linked documentation. No connection, firewall change or live server restart was performed for this article.