Before you start
Record the exact message, the time and timezone, FiveM version, FXServer artifact and recent changes. Copy the address and port from the panel instead of assuming port 30120. Keep client and server logs. Back up affected configuration files and have a rollback plan before changing them. Remove passwords, licence keys, tokens and personal data before sharing diagnostic material.
Find who is affected and where loading stops
Establish whether the problem affects one player, one internet provider or the whole community. Compare a normal connection with another authorised connection without running many attempts at once. An isolated failure may involve the client, DNS, routing or local filtering. If everyone fails after an update, investigate that change first.
Record the displayed stage and errors in the F8 console. Failure to connect, a stalled download and a loading screen after downloads point to different components. Change one thing at a time and record what each test shows.
Check the assigned address and ports
Try a direct connection in FiveM’s F8 console using the assigned game address and port. This separates joining through the public server list from reaching the server itself. The txAdmin administration port is not a substitute for the game port.
Check that FXServer has started, its endpoints match the allocation and networking rules cover the required protocols. A successful TCP test does not establish that UDP works. For managed hosting, use the panel settings and request an allocation check before changing host firewall rules.
Isolate resource files and dependencies
When downloads or loading stop, look for a named resource in the errors. Check its dependencies, paths and required files. An incompatible or missing resource can fail even when hardware capacity is available. Database access must work as well when the framework depends on it.
Reproduce the problem on a test copy with a minimal resource set, then add extensions back gradually. Do not randomly disable scripts on a live community server. Check file sizes and free space: moving a large resource to a cache does not repair its script or dependency errors.
Separate connection proxying, files and game traffic
An HTTP reverse proxy may handle part of the connection process and downloads. Game traffic also uses a separate endpoint, including UDP. An accessible website or FXServer HTTP response therefore does not validate the entire player path. Check each component and proxy logs when your architecture includes one.
Compare advertised addresses, connection endpoints and file destinations with the documentation for your version. An exposed origin address can bypass remote protection. Confirm routing and covered traffic before restricting the origin: blocking a legitimate service, voice traffic or a required port can worsen the outage.
Check workload and artifact compatibility
Review CPU, memory, storage and logs while the failure happens. A single spike is not enough to establish a cause; look for a correlation with failures and running scripts. CPU saturation, database errors or a full disk can delay loading without a network attack.
Before changing artifacts, check framework and resource prerequisites, back up and test the chosen version. FiveM for GTA V Enhanced introduces changes that can conflict with Legacy configurations. A newer artifact being available does not automatically certify your installation, scripts or hosting template as compatible.
Give support evidence they can use
If the problem continues, prepare the time, affected networks, loading stage, useful errors and tests already performed. Include the server version, last change and matching measurements. Support can then compare application logs, port allocations and network information without repeating the entire investigation.
If you suspect an attack, request correlation with mitigation events or network measurements. A timeout alone does not demonstrate a DDoS attack. Avoid repeated restarts, improvised load testing and globally disabling security: these can obscure the cause or create another outage.
For your situation
| Situation | Next check |
|---|---|
| One player cannot join | Compare their message, client, DNS and connection with a player who can join. Then check whether a particular provider or route is affected. |
| Files do not download | Examine resource errors and HTTP or cache destinations. Check files and dependencies before modifying game traffic. |
| Nobody can join | Check startup, assigned ports, the latest change and logs. Request network evidence before concluding that an attack is responsible. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.