Reverse Proxy troubleshooting
Players can’t connect
Section titled “Players can’t connect”- Is the server running? The page header should show Online. If not, start your FiveM server
- Is the
server.cfgblock in place? Check it is there in full and that the server was restarted after adding it - Is a firewall blocking the proxy? At OVH, add the Network Firewall rule. Elsewhere, allow the
sv_proxyIPRangesranges - 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_listingIpOverrideandsv_listingHostOverridelines: they must contain your proxy address - Your
sv_licenseKeymust be valid andsv_master1must 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.
Voice chat doesn’t work for everyone
Section titled “Voice chat doesn’t work for everyone”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.
My custom domain stays pending
Section titled “My custom domain stays pending”- Check that the
CNAMEandTXTrecords are exactly those shown in the Domains tab - On Cloudflare, the
CNAMEmust be DNS only (grey cloud) - Give DNS time to propagate (up to a few hours). See Add your own domain
My server is still being attacked
Section titled “My server is still being attacked”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.
