Troubleshooting common problems
In short
Most server problems follow a handful of patterns. Find the symptom, check the likely cause, then open the linked guide.
| Symptom | Likely cause | First thing to try |
|---|---|---|
| Not in the server list | Ports, active sv_master1, missing project name/description, or just started | info.json test, direct connect, wait up to 8 minutes |
| “Failed to start resource” | Started from the wrong folder, or no fxmanifest.lua | Start from server-data; check the manifest |
| Stuck downloading on join | Huge or broken streamed files | Check oversized-asset warnings; remove the last resource added |
| Only 48 slots | No subscription on the key owner’s account | Element Club Argentum or higher, then raise sv_maxclients |
| Hitch warnings during play | A resource blocking the server thread | profiler record while it happens |
| Missing minimap or texture loss | Conflicting minimap resources, oversized textures | Keep one minimap resource; compress textures |
| Slow startup on Windows | Defender scanning FXServer files | Add a Defender exclusion |
| Crash on join | A broken streamed asset or game build mismatch | Read the crash dump; remove recent assets |
| Desync and rubber-banding | Server hitches, bad connections, client-only state | Profile the server; sync state through the server |