How to Set Up Your First FiveM Server in 2026 (No Fluff)

If you've ever spent four hours staring at server.cfg wondering why your friend's join keeps timing out, this is the guide you wish you had.

This walkthrough is for people who actually want to launch a working FiveM server today — not for people who want a 60-page theoretical PDF. We'll get the server running, then make it good.

What you actually need before you start

You need three things and three things only: a Windows VPS or a decent home PC with port 30120 open, a free Cfx.re license key from keymaster.fivem.net, and a copy of the latest FXServer Windows build. Skip Linux for your first server unless you already love a terminal — Windows builds are easier to troubleshoot when something breaks at 2am.

The 15-minute install path

Drop FXServer into a clean folder like C:\fxserver. Inside, create a server-data folder and clone the official cfx-server-data repo into it. That gives you a working baseline with the [casino], [gameplay], and [system] resources already wired up.

Now create your server.cfg file. Don't paste a 500-line config from someone's GitHub — start with the official template and add only what you need: sv_hostname, sv_licenseKey, endpoint_add_tcp and endpoint_add_udp lines, your admin steam hex, and an ensure line for each resource you actually want.

The mistakes that cost you a weekend

The two most common new-owner mistakes are forgetting to forward UDP (not just TCP) on port 30120, and pasting a license key that's already linked to a different IP. The keymaster panel will show you which IP a key is bound to — re-link it before you swear at the console.

The third mistake is loading 80 resources on day one. Don't. Add five. Get them stable. Then add the next five. You'll thank yourself when something starts crashing and you have a small surface area to debug.

Wrapping up

Once the server boots and you can connect from the in-game direct connect screen, you've crossed the hardest line. Everything from here — frameworks, MLOs, custom scripts — gets layered on top of this foundation. Take a screenshot of your working server.cfg so future-you has a known-good baseline to roll back to.