Skip to content

Reverse Proxy troubleshooting

  1. Is the server running? The page header should show Online. If not, start your FiveM server
  2. Is the server.cfg block in place? Check it is there in full and that the server was restarted after adding it
  3. Is a firewall blocking the proxy? At OVH, add the Network Firewall rule. Elsewhere, allow the sv_proxyIPRanges ranges
  4. Is the backend address right? The IP and port shown in the header (Backend) must be your server’s. If you changed server or port, open a ticket

My server doesn’t show in the FiveM list

Section titled “My server doesn’t show in the FiveM list”
  • Check the sv_listingIpOverride and sv_listingHostOverride lines: they must contain your proxy address
  • Your sv_licenseKey must be valid and sv_master1 must not be empty
  • The list updates every few minutes: wait a little after the restart

All players have the same IP (bans, txAdmin)

Section titled “All players have the same IP (bans, txAdmin)”

This means the sv_proxyIPRanges line is missing or incomplete: FiveM then sees the proxy’s IP instead of the players’. Copy the full block again from the portal and restart.

Check that mumble_maxClientsPerIP 1024 is in server.cfg: without it, voice limits the number of players coming from one IP, and they all come through the proxy IPs.

  • Check that the CNAME and TXT records are exactly those shown in the Domains tab
  • On Cloudflare, the CNAME must be DNS only (grey cloud)
  • Give DNS time to propagate (up to a few hours). See Add your own domain

If the attack hits your server’s IP directly, that IP is known: the proxy can only protect traffic that goes through it. Only share the proxy address or your domain from now on, and ask your host for a new IP if needed.

Still stuck? Open a ticket with the service ID (RPX-…) and the time of the issue.