Set up a FiveM or RedM server behind PlaySafe game protection, with the connect address, the server.cfg block from the panel and the default rules.

FiveM and RedM Setup

This guide is for a FiveM or RedM server behind game protection. It assumes the protection is deployed and Active. If not, start with Deploy Game Protection.

Your connect address

The connect slug you chose on the deploy page becomes your players’ address:

connect your-slug-svr.playsafe.dev

You find it in three places on the protection page (Security > Game protection > your protection):

In the header, under the name
In the Player connect address box of the Overview tab, with a Copy connect button that copies the full connect ... command
In the last step of the Installation Guide (Ready to connect)

The slug cannot be changed from the panel. If you need a different one, open a ticket.

server.cfg

Open the protection and go to the Overview tab.
Expand Installation Guide if it is closed.
In step 1, Update your FiveM Server Configuration (or RedM), use the copy button to copy the configuration block. The block contains your backend IP, so it is hidden on screen. The eye icon shows it after a warning that asks you not to share it or show it on stream.
Paste the block into your server.cfg and restart the server.

Use the block exactly as the panel shows it: it is generated for your protection, with your connect address and backend IP.

Do not stream your config

The block includes your backend IP. Copy it with the copy button instead of revealing it, especially if you are recording or streaming.

Default rules

When a FiveM or RedM protection becomes active, its Rules tab shows three rules:

#	Rule	What it does
1	FiveM Filter (or RedM Filter)	The game filter on UDP port 30120, managed by PlaySafe (shown with a lock)
19	txAdmin Access Deny	Blocks TCP port 40120 (txAdmin) from the internet
20	RDP Access Deny	Blocks TCP port 3389 (Remote Desktop) from the internet

The rules of a game protection are managed by PlaySafe. To let your admins reach txAdmin or your developers reach RDP, or to change the default ports, open a ticket from Tickets with the IPs that need access. The Rules tab of FiveM and RedM protections has a Need help with your configuration? box that links to tickets.

Lock down the server itself

Once players use the connect address, nobody should reach the game port on your backend IP directly. In your server’s own firewall, allow the game port only from the addresses PlaySafe forwards from. Ask support for the current list in a ticket.

Keep your remote access (RDP or SSH) restricted to your own IPs.

Tell your players

Players must use the new connect address. Replace the old IP everywhere you shared it:

Discord announcements and pinned messages
Your website, forum or server list pages
Saved favourites: ask players to remove the old entry

✦

Old IP, no protection

A player who connects with the raw IP goes around the protection. Once everyone has moved, consider asking your provider for a new backend IP so the old one stops working for attackers too.

Check it works

Run connect your-slug-svr.playsafe.dev in the F8 console.
Check that the server console shows the connection.

Symptom	Likely cause
Connect address does not answer	The protection is not Active yet, or the server is not running
Server is listed but you cannot join	The `server.cfg` block is missing or the server was not restarted
Staff cannot open txAdmin	Port 40120 is blocked by default; open a ticket

Next steps

🛡️

The Protection Page

Overview tab, renewal and sharing.

🔔

Attack Notifications

Get a Discord or email message when an attack starts and ends.