Gaming4Free — Free Game Server Hosting G4F.GG v1.0 // FREE FOREVER
BACK TO BLOG
HOME / BLOG / Server Guides
Server Guides

Run a FiveM Server for GTA RP (No BS Setup Guide)

If you have ever tried to run GTA RP with just a Discord channel and vibes, you already know what happens.

Someone can’t connect. Someone’s game crashes. Someone’s stuck in the loading screen for 12 minutes. Your “serious RP” turns into 9 people asking “what’s the IP again”.

So yeah. Having your own FiveM server fixes a lot of that. Not everything. People will still argue about cop SOPs at 2am. But at least you control the server, the rules, the scripts, the economy, the jobs, the whole vibe.

This guide is the “do it the normal way, without losing your mind” walkthrough. We’ll cover hosting options, setup, key configs, scripts, permissions, and keeping the server stable for an RP crew.

What you actually need before you start

Let’s keep it simple. To run a FiveM server, you need:

  • A legit copy of GTA V for anyone playing (FiveM requires it)
  • A server machine (or hosting) that stays online
  • A server build (FXServer)
  • A framework (optional, but almost everyone uses one)
  • A few core resources (spawn, chat, admin, jobs, etc)
  • Some patience

And, realistically:

  • A Discord server for comms and whitelisting
  • A way to do basic troubleshooting (reading logs, restarting resources)
  • Clear rules so your friends don’t turn the city into a perpetual car meet

Step 1. Pick how you want to host it

You have three common options:

Option A: Host on your own PC

This is fine for testing. It’s also fine for a tiny crew if your PC is strong and your upload speed is decent.

The downside is obvious. If your PC sleeps, updates, crashes, or you launch a different game, your RP city goes with it. Also your home network is now the “data center”.

Option B: Rent a VPS or dedicated server

More control, more stability, more cost. This is the traditional route for serious servers.

You’ll be doing more Linux/Windows server stuff yourself, unless you’re already comfortable with it.

Option C: Use a game server host with a control panel

This is what most crews should do, especially if you want to spend your time setting up RP instead of babysitting services.

If you want a quick way to deploy without a credit card, Gaming4Free (https://gaming4free.net) is a solid option to start with. It’s basically “spin up a server, manage it in a web panel, use SFTP, live console, backups, regions, DDoS protection” without needing to commit money upfront. The free tier runs on a 24 hour renewable lease. Paid plans remove the renewal prompts and add priority features.

For crews, the biggest win is this: you can hand off management to a couple admins without giving them your personal PC access. Just panel access. Cleaner. Safer. Less drama.

Step 2. Understand what “FiveM server” means (FXServer)

FiveM servers run on something called FXServer, which is the server artifact build. You download it, configure it, then run it with a config file.

Inside the server you’ll have:

  • server.cfg (your main config)
  • resources/ folder (scripts, frameworks, maps, cars, etc)
  • Cache files and logs
  • Permissions config (ACE permissions, identifiers)

Most of the “running a server” job is just managing that resources folder and keeping server.cfg sane.

Step 3. Install FXServer (the normal way)

If you’re using a host like Gaming4Free, you usually get 1 click setup for FiveM or at least a base template. That saves time.

But if you’re installing manually, the flow is:

  1. Create a folder for your server, like C:\FXServer\server-data (Windows) or /home/fivem/server-data (Linux).
  2. Download the latest server artifacts from the official FiveM artifacts page.
  3. Extract it somewhere like C:\FXServer\server.
  4. Create a server.cfg inside your server-data folder.
  5. Run the server executable and point it at your data folder.

On Windows you’ll run FXServer.exe +exec server.cfg. On Linux you’ll run run.sh +exec server.cfg usually.

Your host panel might abstract this away, but it helps to know what’s happening.

Step 4. Create your server.cfg (the part people mess up)

Your server.cfg is the brain. Here is a starter example you can adapt:

cfg sv_hostname "My Crew RP | Serious-ish RP" sets sv_projectName "My Crew RP" sets sv_projectDesc "Private RP server for friends" sv_maxclients 32

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

sv_licenseKey "YOUR_KEY_HERE"

set steam_webApiKey "none"

sv_scriptHookAllowed 0 sets tags "roleplay, rp, whitelist" sets locale "en-US"

ensure chat ensure spawnmanager ensure sessionmanager ensure hardcap ensure rconlog

You’ll need a FiveM license key. You get it from the FiveM keymaster site. This key is tied to the server IP, so if you change hosting later, you regenerate or update it.

Also. Don’t paste random configs from 2019. Some old settings cause weird issues now.

Quick notes that save headaches

  • sv_maxclients: don’t set 128 because it looks cool. If you’re a crew of 10 to 30, keep it realistic.
  • sv_scriptHookAllowed 0: keep it off.
  • Don’t expose RCON to the internet unless you know what you’re doing.

Step 5. Choose your framework (ESX vs QBCore vs “no framework”)

If you want actual RP systems like jobs, money, inventory, housing, police, EMS, etc, you will want a framework.

ESX

Oldest mainstream framework. Tons of scripts exist for it. Lots of forks. It can be great, but you’ll see more variation in quality because everyone has their own version.

QBCore

Modern and popular. Cleaner baseline in many setups, good community support, lots of scripts too. Many newer servers go QBCore.

No framework

If you want simple “hangout RP” with minimal systems, you can run a lightweight server with just a few resources. But the second you want actual gameplay loops, you’ll start reinventing the wheel.

For most GTA RP crews: pick QBCore unless you specifically want ESX because a script you love only exists there.

Step 6. Add resources (and do it in the right order)

Your resources/ folder becomes your city. The easiest way to stay sane is:

  • Use a consistent naming scheme
  • Group resources into folders (if your host supports it)
  • Add one thing at a time, test, then move on

Typical resource categories:

Core / must-haves

  • Framework core (qb-core or es_extended)
  • Database connector if required
  • Permissions/admin tool
  • Basic UI and chat
  • Spawn system

RP systems

  • Jobs (police, EMS, mechanic)
  • Inventory
  • Phone
  • Banking
  • Vehicles, garages
  • Housing

Content

  • MLOs (map interiors)
  • Custom cars
  • EUP/clothing packs
  • Weapons (be careful with balancing)

Quality of life

  • Anti combat log (if you need it)
  • Basic anti cheat (keep expectations realistic)
  • Logging to Discord (joins, bans, deaths)

Then, in server.cfg, you load them with ensure resourceName.

Example:

cfg ensure qb-core ensure qb-smallresources ensure qb-inventory ensure qb-phone ensure qb-policejob ensure qb-ambulancejob ensure qb-mechanicjob

If something fails to start, check the console. Seriously. The console usually tells you exactly what it hates.

Step 7. Set up a database (if your framework needs it)

Most RP frameworks use MySQL.

You’ll need:

  • A MySQL database (MariaDB is common)
  • A user/password
  • A connection string in your config
  • The framework’s SQL import

On hosted platforms, database creation is often included or one click. On a VPS you’ll install MariaDB yourself.

In FiveM, the database connector is commonly oxmysql now.

Example config snippet (varies by setup):

cfg set mysql_connection_string "mysql://user:password@localhost/database?charset=utf8mb4" ensure oxmysql

Then you import the SQL file that comes with your framework or resource pack.

If you skip this step, your server might “start” but nothing saves. Players relog and everything resets. Which is funny once. Then not funny.

Step 8. Make it private (whitelisting and basic access control)

For a crew server, you probably want to keep randoms out. Even if you list it publicly, whitelisting keeps it peaceful.

Simple approach: don’t list it

You can avoid advertising. Remove listing tags, don’t share the IP. Still, someone will share it. Always happens.

Better approach: Discord whitelist

Most frameworks support whitelist scripts that check Discord roles. Basic flow:

  • Players join your Discord
  • They verify
  • You give them a role
  • Server checks role and allows entry

This also makes banning easier.

ACE permissions (admin rights)

Don’t give everyone admin. Give two people admin. Max three. The rest get in game permissions for specific actions.

FiveM uses ACE permissions, and some admin tools abstract it nicely.

Step 9. Add an admin tool early (before you add 50 scripts)

You want an admin menu early for:

  • Teleporting to bug reports
  • Spawning vehicles for testing
  • Handling stuck players
  • Kicking griefers
  • Checking player IDs

Pick one that’s maintained and fits your framework. Don’t install five admin menus at once. They will fight.

Step 10. Performance basics (what keeps your server smooth)

This is where most new servers slowly die. Not from lack of hype. From 300 scripts and 40 of them running at 10ms each.

Here’s the simple performance checklist:

Watch resource CPU time

Use resmon in the server console (resource monitor). If a resource is heavy, you’ll see it.

If one script is chewing CPU, remove it or replace it. No mercy.

Don’t stack overlapping systems

Example: don’t install three different:

  • inventories
  • target/interaction systems
  • phone scripts
  • vehicle key scripts

Pick one ecosystem and stick to it.

Be careful with huge map packs

MLOs are great. Too many MLOs, plus custom cars, plus EUP, and your players will start timing out or crashing. Especially if they have weaker PCs.

Optimize streaming assets

If you add custom cars, learn the basics of:

  • handling.meta sanity
  • ytd/yft sizes
  • number of add-on vehicles

High quality packs are worth paying for sometimes because someone already optimized them.

Step 11. Backups, updates, and the boring stuff that saves your city

Your RP crew will eventually care about persistence. Money, cars, houses, progress. That means backups matter.

Do this:

  • Automatic database backups daily
  • Automatic server file backups weekly (or before big changes)
  • Manual backup before you install anything new

If you use Gaming4Free, you already get a control panel setup where backups and file management are part of the workflow, which helps a lot. Also SFTP access, so you can keep local copies without doing weird file manager gymnastics.

Updating FXServer artifacts

Don’t update on a random Friday night when everyone wants to play.

Do it like a normal person:

  • Backup first
  • Update artifacts
  • Start server
  • Test logins, inventory, jobs
  • Then announce it’s good

Step 12. A practical “first server” setup that works

If you’re overwhelmed, here’s a clean starter plan for a private crew.

Start with:

  • Base FXServer
  • QBCore (or ESX if that’s your preference)
  • oxmysql
  • One inventory system
  • One phone system
  • Police + EMS jobs
  • One garage system
  • One admin tool
  • Discord whitelist
  • A couple MLOs (like a PD and a hospital)
  • A small pack of cars, not 200

Then play on it for a week.

Only after your crew actually uses it, add more. Because you’ll learn what you really need. Half the “cool scripts” you see on TikTok are pointless for a small crew. They look good in a showcase video though.

Step 13. Troubleshooting. The stuff you will run into

“Connection failed”

Usually:

  • Wrong IP/port
  • Server not actually running
  • Firewall issue (self hosting)
  • License key/IP mismatch

“Resource failed to load”

Usually:

  • Missing dependency
  • Wrong load order
  • Old resource not compatible with your framework version

Read the error. It’s almost always obvious.

Players spawning in the ocean or falling forever

Spawn script conflict. Or missing map resource. Or framework not starting.

Database not saving

  • Connection string wrong
  • oxmysql not started before framework
  • SQL not imported
  • DB user permissions missing

Everyone is desyncing

Often:

  • Too many heavy scripts
  • Server hardware limits
  • Bad network route
  • Too many streamed assets

Also sometimes it’s just one player with a toaster PC. Not always your fault. But you still get blamed.

Step 14. Running the RP side (because the server is only half of it)

A FiveM server can be technically perfect and still feel dead. RP is a social game. So set these expectations early:

  • What type of RP is this. Serious, semi serious, chill, whatever
  • How cops should behave (and how many cops needed to run pursuits)
  • New character rules (do you allow alts)
  • Economy rules (do you wipe, do you keep it stable)
  • Consequences (gear fear, permadeath, jail times)
  • Staff structure (who can ban, who can spawn items, who can approve businesses)

Keep it short. A huge rulebook nobody reads is just cosplay. A one page ruleset that’s enforced consistently works better.

A simple way to get started without overbuilding

If your goal is “my friends want a city we control”, don’t start by renting a giant dedicated machine and installing 120 scripts.

Start smaller. Spin up a FiveM server on a host with a control panel so you can focus on the RP experience.

If you want a no credit card option to test and iterate, check out Gaming4Free at https://gaming4free.net. Deploy, get your IP, upload resources via file manager or SFTP, use the live console, and you’re basically off. If your crew sticks with it, then you can decide if you want to stay on the free renewable lease model or move to a paid plan for convenience.

Let’s wrap this up

Running a FiveM server for your GTA RP crew is not hard in one big step. It’s hard in a hundred small ones. Configs. Dependencies. Script conflicts. The one guy who insists his custom car pack is “optimized” when it’s clearly not.

But once you have:

  • a stable host
  • a clean framework setup
  • a small set of core scripts
  • backups
  • whitelist and permissions

It gets fun. Like actually fun. You stop fighting the server and start building stories.

And that’s the point anyway. The server is just the stage. Your crew makes it worth running.

FAQs (Frequently Asked Questions)

What do I need before starting to run a FiveM server for GTA RP?

To run a FiveM server, you need a legit copy of GTA V for all players, a server machine or hosting that stays online, the FXServer build, optionally a framework (like ESX or QBCore), core resources (spawn, chat, admin, jobs), patience, a Discord server for communication and whitelisting, basic troubleshooting skills such as reading logs and restarting resources, and clear rules to maintain order in your RP community.

What are the common hosting options for a FiveM server and which one is recommended?

There are three main hosting options: A) Hosting on your own PC—good for testing or very small crews but unstable if your PC sleeps or crashes; B) Renting a VPS or dedicated server—offers more control and stability but requires more technical know-how; C) Using a game server host with a control panel—recommended for most crews as it simplifies deployment and management. Services like Gaming4Free provide free tiers with easy web panel management without upfront costs.

What is FXServer and what does running a FiveM server involve?

FXServer is the official server artifact build used to run FiveM servers. Running a FiveM server involves downloading FXServer, configuring it via files like 'server.cfg', managing the 'resources/' folder containing scripts and mods, handling permissions with ACE permissions and identifiers, and maintaining server stability through proper configuration and resource management.

How do I install FXServer manually for my FiveM RP server?

To install FXServer manually: 1) Create a dedicated folder for your server data (e.g., 'C:\FXServer\server-data' on Windows); 2) Download the latest server artifacts from the official FiveM page; 3) Extract them into a folder like 'C:\FXServer\server'; 4) Create your 'server.cfg' configuration file inside your data folder; 5) Run the FXServer executable pointing to your config file (e.g., 'FXServer.exe +exec server.cfg' on Windows). Hosting panels may automate this process.

What should I include in my 'server.cfg' file to avoid common issues?

Your 'server.cfg' should include key settings such as sv_hostname (your server name), sv_maxclients (realistic player limit based on crew size), endpoint ports (TCP/UDP), your unique FiveM license key from the keymaster site, steam_webApiKey if applicable, script hook allowance set to 0 for security, tags describing your server type, locale settings, and essential resource ensures like chat and spawnmanager. Avoid outdated configs from old guides as they can cause issues. Also, don't expose RCON to the internet unless you understand the risks.

Should I use a framework for my FiveM RP server and which ones are common?

If you want robust roleplay systems such as jobs, economy, inventory, housing, police roles, EMS services, etc., using a framework is highly recommended. The most common frameworks are ESX—the oldest and widely used—and QBCore. Frameworks provide structured scripts and resources that make managing complex RP features easier compared to running without any framework.

Frequently Asked Questions

What do I need before starting to run a FiveM server for GTA RP?

To run a FiveM server, you need a legit copy of GTA V for all players, a server machine or hosting that stays online, the FXServer build, optionally a framework (like ESX or QBCore), core resources (spawn, chat, admin, jobs), patience, a Discord server for communication and whitelisting, basic troubleshooting skills such as reading logs and restarting resources, and clear rules to maintain order in your RP community.

What are the common hosting options for a FiveM server and which one is recommended?

There are three main hosting options: A) Hosting on your own PC—good for testing or very small crews but unstable if your PC sleeps or crashes; B) Renting a VPS or dedicated server—offers more control and stability but requires more technical know-how; C) Using a game server host with a control panel—recommended for most crews as it simplifies deployment and management. Services like Gaming4Free provide free tiers with easy web panel management without upfront costs.

What is FXServer and what does running a FiveM server involve?

FXServer is the official server artifact build used to run FiveM servers. Running a FiveM server involves downloading FXServer, configuring it via files like 'server.cfg', managing the 'resources/' folder containing scripts and mods, handling permissions with ACE permissions and identifiers, and maintaining server stability through proper configuration and resource management.

How do I install FXServer manually for my FiveM RP server?

To install FXServer manually: 1) Create a dedicated folder for your server data (e.g., 'C:\FXServer\server-data' on Windows); 2) Download the latest server artifacts from the official FiveM page; 3) Extract them into a folder like 'C:\FXServer\server'; 4) Create your 'server.cfg' configuration file inside your data folder; 5) Run the FXServer executable pointing to your config file (e.g., 'FXServer.exe +exec server.cfg' on Windows). Hosting panels may automate this process.

What should I include in my 'server.cfg' file to avoid common issues?

Your 'server.cfg' should include key settings such as sv_hostname (your server name), sv_maxclients (realistic player limit based on crew size), endpoint ports (TCP/UDP), your unique FiveM license key from the keymaster site, steam_webApiKey if applicable, script hook allowance set to 0 for security, tags describing your server type, locale settings, and essential resource ensures like chat and spawnmanager. Avoid outdated configs from old guides as they can cause issues. Also, don't expose RCON to the internet unless you understand the risks.

Should I use a framework for my FiveM RP server and which ones are common?

If you want robust roleplay systems such as jobs, economy, inventory, housing, police roles, EMS services, etc., using a framework is highly recommended. The most common frameworks are ESX—the oldest and widely used—and QBCore. Frameworks provide structured scripts and resources that make managing complex RP features easier compared to running without any framework.

READY TO START HOSTING?

Deploy your free game server in under 60 seconds. No credit card, no trial — free forever.

DEPLOY FREE SERVER →