Endpoints, ports, and going public

Track A promised that players connect, but a fresh server only ever let you connect from your own machine. This lesson teaches the network path a stranger's game has to travel to reach you: the listening endpoint, the single port 30120 on both TCP and UDP, the router that forwards it, and the firewall that lets it through. You build the cfg block and then prove it works by having a friend connect to your public IP.

You'll build: A server.cfg network block (endpoint_add_udp, endpoint_add_tcp, sv_endpointPrivacy, sv_maxClients) plus a friend-connects-by-IP test
Time: ~30 minutes
You need: A running FXServer you can start, edit server.cfg on, and restart.
You'll learn: endpoint_add_udp/tcp 0.0.0.0:30120 -> why 30120 is TCP and UDP -> sv_endpointPrivacy -> sv_maxClients -> port-forwarding on a home router -> firewall allow -> verifying with a real connection

BEFORE YOU START

Build it

Make a config resource folder

The server has one folder that holds your network convars.

Keeping network settings in their own file makes them easy to find and copy between servers. Inside your server's resources folder, create this folder:

code

resources/qu_server_cfg_endpoints_ports

Name	Protocol	External port	Internal IP	Internal port
FiveM TCP	TCP	30120	192.168.1.50	30120
FiveM UDP	UDP	30120	192.168.1.50	30120

Endpoints, ports, and going public

Build it

Make a config resource folder

Create the files

Write fxmanifest.lua

Write the network block

Load network.cfg from server.cfg

Start the server and read the console

Keep reading the full lesson