Protect the actual FiveM TCP and UDP connection upstream with your host or network provider. A local firewall helps control exposure, but it cannot restore a link already saturated by traffic.
Map the connection paths
Record the HTTP connection endpoint, game endpoint, public origin and management access. Include old addresses that still reach the server. The official proxy documentation distinguishes the connection and game traffic paths.
Ask the provider which protocols and ports its mitigation covers, how incidents are detected, what operating limits apply and how to escalate. Website-only protection is not proof of game-endpoint coverage.
Restrict exposure without locking yourself out
- Back up the current firewall and network configuration. Keep an independent management recovery path before changing access rules.
- Expose only the game ports you use; restrict SSH, RDP, database and administration services to authorized access paths. Test from an authorized management client.
- If using a supported game proxy, route every public connection path through it and restrict the origin to the required mitigation network and management sources. Verify the provider’s address ranges and health checks.
- Test a real client join and an administrator connection before closing the maintenance window. Restore the saved rules immediately if required traffic fails.
Prepare an incident runbook
Record normal packet rate, bandwidth, connection failures and FXServer health. Set alerts with an actionable threshold based on your baseline. Keep the provider’s escalation route, service identifier and an independent player status channel available.
During an incident, capture UTC times, affected endpoints, traffic measurements and provider incident IDs. Avoid sharing player identifiers, secrets or unrestricted packet captures publicly. Distinguish a resource crash from network saturation before changing resources.
Recover and learn
Confirm that legitimate clients can connect and that game and management services are healthy before declaring recovery. Review whether traffic reached an old origin path and whether the provider’s mitigation covered the actual protocol.
Keep restorable backups for data recovery, but do not present backups as a DDoS mitigation. No setup can promise uninterrupted service.