How to Host a FiveM Server Without Port Forwarding in 2026

Hosting a FiveM server usually requires opening port 30120 on your router. But that isn't always possible, especially if your ISP uses CGNAT, you don't have access to the router, or inbound ports are blocked.

You can still make your FiveM server publicly accessible.

In this guide, we'll use Portwarp to expose a local FXServer without port forwarding, a public IPv4 address, or any router configuration.

By the end, players will be able to connect using an address similar to myserver.pwrp.cc:18472.

What you'll need

• A working FXServer or txAdmin server
• FiveM running locally on port 30120
• Portwarp installed on the same device
• No router access or public IPv4 required

FiveM uses TCP and UDP on its game endpoint, so both protocols need to be available through the tunnel.

Free vs PRO for FiveM

You can host a FiveM server with Portwarp Free and let players join using Direct Connect:

connect myserver.pwrp.cc:18472

If you want the server to appear correctly in the FiveM public server list, you'll need Portwarp PRO.

The public list requires FiveM's listing backend to access your server through an HTTPS/SSL endpoint. Portwarp provides this functionality for FiveM servers on PRO.

PRO also includes features such as Portless Address.

So if you're hosting a server for friends, Free is enough to get started. If you want public discovery through the FiveM server browser, use PRO.

Step 1: Start your FiveM server

Start FXServer normally through txAdmin or your existing setup.

Your server.cfg should usually contain:

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

Keep port 30120. You don't need to change it to the public port Portwarp assigns later.

Before continuing, check that FXServer works locally by opening:

http://127.0.0.1:30120/info.json

You should receive JSON information about your server.

You can also open FiveM, press F8, and test:

connect 127.0.0.1:30120

If the server doesn't work locally, fix that first. Portwarp forwards traffic to your existing FXServer, so the local server needs to be working before the tunnel can expose it.

Step 2: Install Portwarp

Install Portwarp on the same computer running your FiveM server and sign in to your account.

You can use the Portwarp desktop app or CLI depending on your setup.

Only the server needs Portwarp. Players don't need to install anything.

Step 3: Create the FiveM tunnel

Create a new tunnel using the FiveM preset.

Use:

• Local port: 30120
• Protocol: TCP + UDP

Start the tunnel and Portwarp will assign a public address similar to:

myserver.pwrp.cc:18472

Your actual hostname and port will be different.

Traffic now follows this path:

Players
   ↓
myserver.pwrp.cc:18472
   ↓
Portwarp
   ↓
127.0.0.1:30120
   ↓
FXServer

No router configuration is required.

Why TCP + UDP?

FiveM uses both protocols on its game endpoint.

Don't create only a TCP or UDP tunnel. The FiveM tunnel should use TCP + UDP so both types of traffic reach FXServer correctly.

Step 4: Test Direct Connect

Before configuring the public server list, make sure the tunnel itself works.

Open FiveM, press F8, and run:

connect myserver.pwrp.cc:18472

Replace the example with the public address shown by Portwarp.

If you can join the server, the tunnel is working and you can share the same address with other players.

Don't change your local FiveM port

If Portwarp gives you myserver.pwrp.cc:18472, don't change FXServer to port 18472.

Your server should still use:

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

Port 30120 is the local FXServer port. The Portwarp address and port are the public endpoint.

For example:

Local FXServer: 127.0.0.1:30120
Public endpoint: myserver.pwrp.cc:18472

Portwarp handles the mapping between them.

Step 5: Configure the FiveM public server list

This step requires Portwarp PRO. If you only need Direct Connect, you can stop at the previous step.

FiveM's public server list works differently from Direct Connect.

When using an indirect listing or proxy, the FiveM listing backend needs to reach your server through an HTTPS endpoint. Portwarp PRO provides the SSL/HTTPS functionality required for this setup.

Keep your normal local endpoints:

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

Then add the public listing configuration:

set sv_forceIndirectListing true
set sv_listingHostOverride "myserver.pwrp.cc"
set sv_endpoints "myserver.pwrp.cc:18472"
set sv_proxyIPRanges "127.0.0.1/32"

Replace myserver.pwrp.cc and 18472 with your Portwarp address.

Notice that sv_listingHostOverride contains only the hostname:

set sv_listingHostOverride "myserver.pwrp.cc"

While sv_endpoints contains the hostname and public game port:

set sv_endpoints "myserver.pwrp.cc:18472"

Remove sv_listingIpOverride

If an older guide told you to configure sv_listingIpOverride, remove or comment it out.

The Portwarp setup should use:

set sv_forceIndirectListing true
set sv_listingHostOverride "myserver.pwrp.cc"
set sv_endpoints "myserver.pwrp.cc:18472"
set sv_proxyIPRanges "127.0.0.1/32"

Also make sure this remains commented in your configuration:

#sv_master1 ""

After making the changes, restart FXServer itself.

Step 6: Check the HTTPS endpoints

Before waiting for your server to appear in the FiveM browser, verify that FiveM can retrieve the server information through HTTPS.

Open:

https://myserver.pwrp.cc/info.json
https://myserver.pwrp.cc/players.json
https://myserver.pwrp.cc/dynamic.json

All three endpoints should respond correctly.

If they don't, the FiveM listing backend won't be able to retrieve your server information.

Once Direct Connect works, the HTTPS endpoints are available, and FXServer has been restarted with the correct configuration, your server can be advertised through the FiveM public server list.

Hosting FiveM behind CGNAT

CGNAT is one of the most common reasons port forwarding doesn't work.

Normally, hosting a server requires traffic to reach your public IPv4, then your router, and finally the port forwarding rule that points to FXServer.

With CGNAT, your ISP may share one public IPv4 between multiple customers. Incoming connections therefore never reach your router directly.

Portwarp works differently. Your device creates an outbound connection to the Portwarp network:

FXServer
   ↓
Portwarp connection
   ↓
Portwarp network
   ↑
Players

Because the connection starts from your device, you don't need a public IPv4 or an inbound port forwarding rule.

This makes Portwarp useful for FiveM servers running behind CGNAT, mobile or 5G connections, apartment networks, dorm networks, or routers you don't control.

Troubleshooting

Portwarp is online, but FiveM doesn't work

First check:

http://127.0.0.1:30120/info.json

If that doesn't respond, troubleshoot FXServer before Portwarp.

The server works locally, but players can't connect

Make sure your tunnel points to 127.0.0.1:30120 and uses TCP + UDP.

Then test the public address directly:

connect myserver.pwrp.cc:18472

Portwarp gave me a port other than 30120

That's normal.

Your setup might look like:

Local:  127.0.0.1:30120
Public: myserver.pwrp.cc:18472

Players use the public Portwarp port. FXServer continues using its local port 30120.

Direct Connect works, but my server isn't in the FiveM server list

First check your Portwarp plan.

The FiveM public server list integration requires PRO because the listing backend needs the HTTPS/SSL endpoint provided by Portwarp.

If you're already using PRO, verify:

set sv_forceIndirectListing true
set sv_listingHostOverride "myserver.pwrp.cc"
set sv_endpoints "myserver.pwrp.cc:18472"
set sv_proxyIPRanges "127.0.0.1/32"

Then check:

https://myserver.pwrp.cc/info.json
https://myserver.pwrp.cc/players.json
https://myserver.pwrp.cc/dynamic.json

If those endpoints work, restart FXServer and check the server list again.

I'm using Free and my server isn't in the FiveM browser

That's expected.

Portwarp Free lets players connect directly to your FiveM server using the public hostname:port, but the FiveM public server list integration requires PRO.

Players can still join using:

connect myserver.pwrp.cc:18472

Do I need to expose txAdmin?

No.

txAdmin is separate from the FiveM game endpoint and doesn't need to be publicly exposed for players to join.

Don't expose your administration interface just to make the game server accessible.

Do players need Portwarp?

No.

Only the device hosting FXServer needs Portwarp.

Players connect normally through FiveM using:

connect myserver.pwrp.cc:18472

They don't need a Portwarp account, VPN, or additional client.

Can I use a Portless Address?

Yes. Portless Address is available with Portwarp PRO for supported game tunnels.

Instead of sharing a hostname with a random public port, you can use a cleaner Portwarp game address while FXServer continues listening locally on port 30120.

Portless Address is optional and isn't required for Direct Connect to work.

Host FiveM without port forwarding

Your final setup looks like this:

FXServer
127.0.0.1:30120
        ↓
     Portwarp
        ↓
Public Portwarp address
        ↓
     Players

With Portwarp Free, players can connect directly using your public address.

With Portwarp PRO, you can also configure the SSL/HTTPS endpoint required for the FiveM public server list and use features such as Portless Address.

You don't need to change your router, request a dedicated public IPv4, or move your FiveM server to a VPS just because your ISP uses CGNAT.

Start FXServer, connect Portwarp, and share your public address.