Public Assetto Corsa servers work until they stop matching how you want to drive. You may want different cars, custom tracks, stricter rules, freeroam traffic, or better uptime. 

Running your own server gives you that control. In this guide, we will break down the two main paths: the official dedicated server for classic race sessions, and AssettoServer for freeroam and traffic setups. 

You will learn how to choose hardware, install the server on Windows or Linux, use Content Manager presets, configure key files, open the right ports, and fix common join issues. 

By the end, you will know when home hosting is enough and when dedicated hosting makes more sense.

Key Takeaways

• You run your own Assetto Corsa dedicated server to control cars, tracks, rules, mods, and who joins.
• You can start free on a home PC, then move to a VPS or RedSwitches dedicated server when player counts, mods, and uptime needs grow.
• Single-thread CPU speed, SSD or NVMe storage, and enough upload bandwidth decide how many players and AI your servers handle smoothly.
• You install the server with the Steam Tool or SteamCMD on Windows, and run it on Linux with Wine or native AssettoServer.
• server_cfg.ini and entry_list.ini define identity, sessions, rules, cars, and drivers, while Content Manager turns this into a visual, preset-based workflow.
• Correct port and firewall settings plus LAN testing prevent most join, lobby, and “server not found” problems.
• When you hit lag, unstable sessions, or limits with multiple instances, moving your presets and content to a RedSwitches machine gives you stable, scalable hosting.

Why Run Your Own Assetto Corsa Dedicated Server in 2026

Public servers work until they clash with how you want to drive. Wrong cars, random rules, restarts with no warning, and admins who vanish. When you host your own Assetto Corsa servers, you control cars, tracks, rules, and who gets in.

You decide if the server runs strict league races or relaxed freeroam. You can lock grids for serious race nights or run open Assetto Corsa mod servers that show off your favourite content. That server becomes a stable home for your friends, Discord, or league.

Home hosting is enough when you drive with a small group, play a few evenings a week, and do not care about 24/7 uptime. Moving to RedSwitches makes sense when you want a public server that always stays online, plan traffic servers with heavy mods, or need low ping for drivers across several regions.

Assetto Corsa Server Types – Official Dedicated Server, AssettoServer, and Content Manager

Official Kunos Assetto Corsa Dedicated Server

The official server remains the foundation for structured Assetto Corsa multiplayer. It handles:

• Practice, qualifying, and race sessions
• Timing, results, and lap data
• Standard lobby visibility and join flow

You install it as a Steam Tool (AppID 302550) and manage it with config files or helper tools. Use it when you host classic race servers, run league seasons with points and ballast, and want behaviour that matches the stock game.

AssettoServer – Freeroam and Traffic Assetto Servers

AssettoServer is a custom Assetto Corsa server built for freeroam setups. It adds features like AI traffic, dynamic weather, and stronger identity checks, but it is not a drop-in replacement for structured race weekends.

Feature	Official Assetto Corsa Dedicated Server	AssettoServer
Main purpose	Classic multiplayer race servers	Practice-only freeroam and traffic servers
Best for	Leagues, race nights, standard online sessions	Shutoko, LA Canyons, AI traffic, CSP-heavy freeroam
Practice / Qualify / Race sessions	Yes	Not the main use case
Lap timing and race flow	Standard race-server behaviour	Limited for race-server use
AI traffic	No	Yes
Dynamic weather	Limited and tooling-dependent	Yes
Steam identity verification	Basic by default	Stronger Steam-based checks
Content Manager workflow	Common and well-supported	Common, but some original-server settings may not work
Linux path	Usually Wine for the official server	Native Linux build available
Safer summary	Use this for traditional race hosting	Use this for freeroam, traffic, and custom server features

Pick AssettoServer when you want practice-only freeroam or traffic servers on maps like Shutoko or LA Canyons, need AI traffic, or want stronger Steam-based identity checks. Keep the official dedicated server for classic race weekends and league sessions.

Content Manager and CSP – The Modern Control Panel

Content Manager has become the main cockpit for hosting Assetto Corsa server presets. With the full version, the Server tab lets you configure everything without editing .ini files by hand.

From one screen you can:

• Pick track, layout, cars, and skins
• Set session lengths, assists, damage, and penalties
• Configure weather, time of day, and time progression

When the preset feels right, you pack it into a server folder and either run it on your own PC for testing or upload it to a VPS, dedicated server, or panel host. 

Custom Shaders Patch (CSP) is the key client-side mod layer for many modern freeroam and traffic setups, while Content Manager remains the main workflow tool for building and packing those presets. 

With CM and the right compatible configs, you move from a basic server to a tailored multiplayer environment.

Choose the Right Assetto Corsa Hosting Setup

You can host Assetto Corsa on a home PC, a VPS, a dedicated server, or a game server panel. The right option depends on your player count, mod load, uptime needs, and how much control you want. Use the quick comparison first, then read the breakdown below to choose the best fit.

Hosting option	Best for	Main strength	Main limit	Good time to upgrade
Home PC	Small private sessions	Free and easy to test	Upload speed and uptime	When players grow or you want 24/7 hosting
VPS	One lean public server	Better uptime and static IP	Shared CPU and disk	When you want AI traffic or several servers
Dedicated server	Traffic, bigger grids, long-term growth	Strong performance and full control	Higher cost and more admin work	When your community grows and stability matters
Game server provider	Fast casual setup	Simple web panel	Less control and flexibility	When you want better value or deeper control

Home PC: Best for Learning and Small Private Sessions

What it is
Your gaming PC runs the server and the game.

Good fit if you want

• A free way to get started
• Full control over files and mods
• Small sessions with friends

What to expect

• Often enough for around 4 to 8 players
• Best with a decent CPU and 10 to 20 Mbps upload
• Good for testing, learning, and short sessions

Main limits

• Your PC must stay on while the server runs
• Upload speed becomes the bottleneck quickly
• Router and port forwarding can be annoying
• Dynamic IPs can create extra hassle

Move on when

• More than 8 to 10 players join often
• Players start complaining about lag
• You want the server online all the time

VPS: Best for One Lean Public Server

What it is
A virtual server rented in a data center.

Good fit if you want

• Better uptime than a home PC
• A static IP
• A simple step up from local hosting

What to expect

• Often enough for around 10 to 24 players
• Common starting point is 2 to 4 vCPU, 4 to 8 GB RAM, and SSD storage
• Good for public race servers, practice servers, and small leagues

Main limits

• CPU and disk are shared with other users
• Heavy mods, traffic, or multiple servers can hit limits fast
• Performance can vary by provider

Move on when

• You want AI traffic
• You want to run several servers
• You see CPU spikes, lag, or rubber-banding

Dedicated Server: Best for Traffic, Bigger Grids, and Growth

What it is
A full physical machine dedicated only for your use.

Good fit if you want

• Stronger CPU performance
• Better room for mods, CSP, plugins, and multiple instances
• Stable long-term hosting

What to expect

• Enough headroom for larger public servers
• Better suited for freeroam traffic setups
• Strong option for communities that want to grow

Main limits

• Higher monthly cost than a small VPS
• Needs basic server admin skills
• Overkill for a very small private group

Choose this when

• You want stable long-term hosting
• You need low ping across regions
• You plan to grow beyond one small server

Game Server Provider: Best for Fast Setup

What it is
A ready-made game server managed through a web panel.

Good fit if you want

• Fast setup
• Minimal technical work
• One simple public server

What to expect

• Easy to start
• Easy to manage
• Fine for casual hosting

Main limits

• Less control over the system
• Less flexibility for advanced mods and tools
• Can cost more per server over time

Move on when

• You want deeper control
• You want better value at scale
• You plan to run more than one server

Quick Choice Guide

• Choose a home PC if you just want to play with friends and learn the basics.
• Choose a VPS if you want one small public server that stays online.
• Choose a dedicated server if you want traffic, bigger grids, or several servers.
• Choose a game server provider if you want the fastest setup with the least technical work.

Storage Requirements for Mod-Heavy Assetto Corsa Servers

Disk speed decides how fast you load tracks, car packs, and CSP content. Capacity decides how many mods you can store before you start pruning.

Baseline storage rules

• Always use SSD or NVMe, not HDD
• Keep at least 20–30 GB free for logs, configs, and future mods

Rough disk budget

• Vanilla content only: 20–30 GB
• Light mods (few tracks and car packs): 40–60 GB
• Heavy mod setups with big packs and CSP content: 80–150 GB+

NVMe shines on busy servers where players change tracks often, or where you run several instances on one host. 

Bandwidth and Latency Targets

CPU handles physics. Bandwidth and latency decide how smooth other cars look on screen.

A simple rule:

• Budget around 0.2–0.4 Mbps upload per player
• Add extra headroom for plugins, HTTP status, and overhead

Examples:

• 10 players → aim for at least 5 Mbps upload
• 20 players → aim for 10 Mbps upload or more

On a home line, the upload cap is usually the first wall. You can have a fast download speed and still see lag if upload tops out.

On a VPS, a 100 Mbps port is enough for one or two servers, as long as the provider does not throttle you. 

On a RedSwitches dedicated server with a 1 Gbps, 10 Gbps or 25Gbps port, you have enough bandwidth to:

• Run multiple Assetto Corsa instances
• Serve players from several regions
• Carry AI traffic updates without spikes

Low latency still matters. Place the server close to most drivers. If your community is split across regions, RedSwitches locations give you flexibility.

Windows vs Linux for Assetto Corsa Dedicated Server

You can host on both Windows and Linux, but the official dedicated server is distributed as a Windows Steam Tool. On Linux, the usual paths are running the official server under Wine or using native AssettoServer for freeroam setups.

Windows

• Native support for the official dedicated server
• Easy pairing with Content Manager and graphical tools
• Familiar environment for most sim racers

Best for:

• Single server or small set of servers
• Admins who want less CLI work
• Hosts who configure everything from a desktop environment

Linux

• Runs the official server under Wine, or runs AssettoServer through its native Linux build
• Fits well with systemd, SSH, scripts, and remote management
• Often lighter on overhead for long-running services

Best for:

• power users comfortable with terminal work
• Multi-server setups on a VPS or dedicated host
• Assetto Corsa dedicated server linux environments with automation and monitoring

On RedSwitches, both options work. Many hosts start with Windows for ease, then move to Linux once they want scripts, containers, or tighter control.

Assetto Corsa Dedicated Server Steam Installation (Windows GUI)

If you host on Windows and prefer a guided setup, installing through Steam is the easiest way to get started. You use the Assetto Corsa dedicated server steam Tool and the built-in server manager before you move to more advanced paths.

Installing the Assetto Corsa Dedicated Server Steam Tool

On the machine that will run the server:

1. Open Steam and log in.
2. Go to your Library, then switch the filter to Tools.
3. Search for “Assetto Corsa Dedicated Server”.
4. Install it like any other Steam entry.

Steam will place the server files under:

…\Steam\steamapps\common\Assetto Corsa Dedicated Server\

You do not need the full game installed on this machine, but it helps when you test locally.

Folder Layout and Key Files

Inside the dedicated server folder you will see:

• acServer.exe – the core headless server process
• acServerManager.exe – GUI helper for generating configs
• cfg\server_cfg.ini – main server configuration
• cfg\entry_list.ini – grid and car configuration

Think of this folder as the “engine room.” The game client on your PC talks to it over the network. For simple home setups, many people later copy parts of this folder into their main game directory to keep content paths simple, which we will cover in a moment.

Using acServerManager for a First Test Server

acServerManager.exe gives you a quick way to generate a working server without editing .ini files by hand.

Basic first run:

1. Start acServerManager.exe.
2. Pick a track and layout from the drop-down list.
3. Add a few car models to the grid.
4. Set:
   • Session type: practice, qualify, race, or just practice
   • Session length in minutes
   • Max clients and passwords if needed
5. Save the configuration.
6. Click the button to start the server.

Then:

• Open Assetto Corsa (or Content Manager) on the same machine.
• Go to the LAN or Online tab.
• Look for your server name and join.

If you can join locally and drive laps, your install and basic config are sound. Only then should you worry about external access and port forwarding.

Copying the Dedicated Server into the Game Folder

Some home hosts prefer to keep the server inside the main game directory:

…\Steam\steamapps\common\Assetto Corsa\server\

They do this because:

• The server and client then share the same content\cars\ and content\tracks\ folders
• Managing mods becomes simpler on a single machine
• You reduce the chance of “car not found” or “track not found” on your own host

To use this pattern:

1. Create a server folder inside your main Assetto Corsa directory.
2. Copy the contents of the dedicated server install into this server folder.
3. Run acServerManager.exe from …\Assetto Corsa\server\.

When you install new cars or tracks for your own client, the official dedicated server can see them as well if both point at the same content tree. Treat this as a home-lab shortcut for the official DS only. Do not use the same approach for AssettoServer, because its docs explicitly warn against extracting it into the main Assetto Corsa folder.

Assetto Corsa Dedicated Server Download with SteamCMD (Windows and Linux)

SteamCMD gives you a clean, scriptable way to install and update the server on both Windows and Linux. You avoid the full Steam client and keep the install small and easy to automate.

Installing and Configuring SteamCMD

On Windows

1. Download SteamCMD from Valve’s site.
2. Extract it to a folder such as C:\steamcmd.
3. Create a subfolder for the server install, for example C:\acserver.

To run SteamCMD:

cd C:\steamcmd

steamcmd.exe

Inside the SteamCMD prompt, many admins use anonymous login for the dedicated server tool. If you prefer to use an account, use a separate Steam account for server administration rather than your main play account.

On Linux

1. Create a folder, for example /opt/steamcmd.
2. Download and extract SteamCMD there.
3. Create an install folder such as /opt/acserver.

Run:

cd /opt/steamcmd

./steamcmd.sh

Inside the prompt, log in the same way.

Assetto Corsa Dedicated Server Download Command

The dedicated server uses AppID 302550. You always point SteamCMD at a specific folder before you pull that AppID.

Windows example

steamcmd +login anonymous ^

  +force_install_dir C:\acserver ^

  +app_update 302550 validate ^

  +quit

Linux example for the official dedicated server under Wine

./steamcmd.sh +@sSteamCmdForcePlatformType windows \

  +login anonymous \

  +force_install_dir /opt/acserver \

  +app_update 302550 validate \

  +quit

After this, your dedicated server files sit in C:\acserver or /opt/acserver.

Running the DS on Windows After SteamCMD Install

Once SteamCMD finishes, you can start the server straight from the install folder.

Basic test:

cd C:\acserver

acServer.exe

The console should print a few lines, then load cfg\server_cfg.ini and cfg\entry_list.ini. For a smoother workflow, create a simple batch file:

@echo off

cd /d C:\acserver

start acServer.exe

Double click this file to launch the server. Watch the console for:

• Errors about missing tracks or cars
• Lobby registration messages
• Port binding errors on 9600 or 8081

If it stays running and prints a lobby line, your install works.

Running the DS Under Wine on Linux

On Linux, you run the Windows server through Wine.

1. Install Wine and any 32/64-bit dependencies your distro needs.
2. Use SteamCMD with the platform flag to install into /opt/acserver.
3. Run the server:

cd /opt/acserver

wine acServer.exe

For a clearer view:

WINEDEBUG=-all wine acServer.exe

Check that:

• The process keeps running
• The console output shows the same log lines you see on Windows
• Ports 9600 and 8081 show as listening (ss -tulnp | grep 9600 etc.)

You can now join from a client and treat this like any other Assetto Corsa server.

Auto-Start and Restart Patterns

You want the server to come back after reboots and crashes. Do not leave it as “I double click an EXE” forever.

On Windows

You have two common options:

• Task Scheduler
  • Create a task that runs at startup or on user logon.
  • Point it at your batch file that starts acServer.exe.
• NSSM (Non-Sucking Service Manager)
  • Install NSSM.
  • Wrap acServer.exe as a Windows service.
  • Set it to restart on exit.

On Linux

Use systemd:

• Create a unit file under /etc/systemd/system/acserver.service.
• Set it to run wine acServer.exe from /opt/acserver.
• Enable and start the service:

sudo systemctl enable acserver

sudo systemctl start acserver

With this in place, the server boots with the OS and restarts if the process exits.

Assetto Corsa Dedicated Server Linux Setup

Linux is a strong base for long-running Assetto Corsa servers. You get clean services, easy logging, and better control over updates. You can run the official server under Wine or switch to native AssettoServer.

DS Under Wine vs Native AssettoServer

You have two main paths on Linux.

Dedicated server under Wine

• Uses the same acServer.exe that runs on Windows
• Keeps behaviour close to the official setup
• Lets you reuse Windows-focused guides and tools

This fits when you:

• Already know the official DS well
• Want race servers with standard timing and sessions
• Prefer to mirror a Windows setup on Linux

Native AssettoServer

• Ships as a Linux binary
• Targets freeroam, AI traffic, and CSP features
• Often runs lighter than Wine in practice

This fits when you:

• Build freeroam and traffic servers
• Plan multiple AI-heavy instances
• Want a cleaner Linux stack with fewer layers

You can run both on a strong host. Many admins use Wine DS for race servers and AssettoServer for traffic servers on the same machine.

Linux Directory Layout and Users

A clean layout makes life easier when you maintain several servers.

You can:

• Run everything under a dedicated user, for example acserver
• Keep installs under /opt or inside that user’s home

Example structure:

/home/acserver/

  ac-tools/           # scripts, helper files

  ac-ds/              # official DS under Wine

    cfg/

    logs/

  ac-assets/          # shared content (cars, tracks, apps)

  ac-assetto-server/  # AssettoServer binaries and configs

Key points:

• Avoid running servers as root
• Give acserver ownership of these folders
• Mount extra disks under clear paths if you need more space for mods

This setup makes it easy to back up configs and separate content from binaries.

Firewall and Ports on Linux

You must open the game and HTTP ports on the Linux firewall. Do not leave the box wide open.

With ufw:

sudo ufw allow 9600/udp

sudo ufw allow 9600/tcp

sudo ufw allow 8081/tcp

sudo ufw allow 8081/udp

sudo ufw enable

With iptables (basic example):

sudo iptables -A INPUT -p udp –dport 9600 -j ACCEPT

sudo iptables -A INPUT -p tcp –dport 9600 -j ACCEPT

sudo iptables -A INPUT -p tcp –dport 8081 -j ACCEPT

sudo iptables -A INPUT -p udp –dport 8081 -j ACCEPT

Lock down admin access:

• Allow SSH only from trusted IPs if possible
• Use SSH keys instead of passwords
• Avoid exposing extra services on the same host

If you sit behind a cloud firewall as well (on a VPS or dedicated server), mirror these port rules there too.

Example systemd Units

Here are simple unit files you can adapt. They keep the server running as a service and restart it if it crashes.

1) Wine + Dedicated Server

Create /etc/systemd/system/acds.service:

[Unit]

Description=Assetto Corsa Dedicated Server (Wine)

After=network.target

[Service]

User=acserver

WorkingDirectory=/home/acserver/ac-ds

ExecStart=/usr/bin/wine acServer.exe

Restart=on-failure

RestartSec=5

StandardOutput=journal

StandardError=journal

[Install]

WantedBy=multi-user.target

Then:

sudo systemctl daemon-reload

sudo systemctl enable acds

sudo systemctl start acds

2) Native AssettoServer

Create /etc/systemd/system/assettoserver.service:

[Unit]

Description=AssettoServer (Freeroam / Traffic)

After=network.target

[Service]

User=acserver

WorkingDirectory=/home/acserver/ac-assetto-server

ExecStart=/home/acserver/ac-assetto-server/assettoserver

Restart=on-failure

RestartSec=5

StandardOutput=journal

StandardError=journal

[Install]

WantedBy=multi-user.target

Enable and start:

sudo systemctl daemon-reload

sudo systemctl enable assettoserver

sudo systemctl start assettoserver

With these units, both the official DS and AssettoServer behave like first-class services on your Linux host. That is the foundation you want before you start stacking mods, traffic, and multiple servers on top.

server_cfg.ini Deep Dive – Control How Your Assetto Corsa Server Works

server_cfg.ini controls how your server looks, feels, and behaves. Once you understand this file, you stop guessing.

Identity and Password Settings

NAME=EU | GT3 Spa | 30 Slots

PASSWORD=

ADMIN_PASSWORD=strong_admin_pass

• NAME – what drivers see in the list. Include region, class, and track. Treat it like a mini ad.
• PASSWORD – empty for public, set a value for private practice or events.
• ADMIN_PASSWORD – grants admin rights via /admin yourpass in chat. Keep this private.

Use a consistent naming scheme if you run several Assetto Corsa servers under one brand.

Track, Layout, and Session Blocks

TRACK=spa

CONFIG_TRACK=gp

• TRACK → content/tracks folder.
• CONFIG_TRACK → layout subfolder (or leave empty for default).

Session structure:

[PRACTICE]

TIME=60

IS_OPEN=1

[QUALIFY]

TIME=20

IS_OPEN=1

[RACE]

LAPS=20

WAIT_TIME=60

IS_OPEN=1

• TIME → minutes for practice/qualifying.
• LAPS → race distance.
• IS_OPEN → allow mid-session joins.

Loop behaviour:

LOOP_MODE=1

• 0 → stop after event.
• 1 → loop same combo or rotation.

Start with one combo and a simple loop. Add rotations later.

Rules, Assists, and Damage

FUEL_RATE=100

TYRE_WEAR_RATE=100

DAMAGE_MULTIPLIER=50

ABS_ALLOWED=2

TC_ALLOWED=2

STABILITY_ALLOWED=1

ALLOWED_TYRES_OUT=2

• FUEL_RATE, TYRE_WEAR_RATE
  • 100 = normal.
  • Raise for strategy, lower for casual driving.
• DAMAGE_MULTIPLIER
  • 0 = no damage, 100 = full.
  • For freeroam/traffic, use ~10–50 to avoid constant pit trips.
• ABS_ALLOWED, TC_ALLOWED, STABILITY_ALLOWED
  • 0 off, 1 factory, 2 free.
  • Public servers: usually ABS/TC free, stability optional.
  • Leagues: ABS/TC factory, stability off.
• ALLOWED_TYRES_OUT

Treat this setting carefully. Public documentation around it is thin, and third-party references still mark its exact behaviour as unclear. Do not present it as a simple linear “lower is stricter, higher is looser” rule without testing it on your own combo.

Match these settings to your audience: more assists and softer damage for public pick-up, stricter for serious racing.

Ports and Network Options

UDP_PORT=9600

TCP_PORT=9600

HTTP_PORT=8081

REGISTER_TO_LOBBY=1

• UDP_PORT – main game traffic; must be open on router and firewall.
• TCP_PORT – used by tools and some join flows.
• HTTP_PORT – lobby and HTTP-related traffic used by the server and helper tools. Treat it as a port that may need both TCP and UDP open, especially when you use external managers or wrapper tools.
• REGISTER_TO_LOBBY – 1 for public lobby, 0 for LAN/direct-IP only.

For multiple servers on one machine, give each its own set:

• Server 1 → 9600 / 8081
• Server 2 → 9601 / 8082
• Server 3 → 9602 / 8083

Plan this before you touch firewalls or NAT.

entry_list.ini Deep Dive – Control Who Drives What

entry_list.ini defines the grid: which cars exist, who owns them, and how strict your access rules are.

Open Public Servers vs Locked League Servers

[SERVER]

LOCKED_ENTRY_LIST=0

• 0 – open server. Drivers pick any allowed car. Ideal for public lobbies.
• 1 – locked list. Only defined GUIDs and slots can join. Ideal for leagues.

With LOCKED_ENTRY_LIST=0, GUID can stay empty. With 1, every slot must have a GUID.

Steam GUIDs, Ballast, and Restrictor

[CAR_0]

DRIVERNAME=Jane Doe

TEAM=RS Racing

MODEL=ks_lamborghini_huracan_gt3

SKIN=01_default

GUID=7656119XXXXXXXXXX

BALLAST=0

RESTRICTOR=0

• GUID – driver’s SteamID64 from their profile or an ID tool. Binds the slot to that account.
• BALLAST – extra weight in kg to slow dominant drivers or balance classes.
• RESTRICTOR – power cut for balance of performance.

For leagues, keep a spreadsheet of drivers, GUIDs, ballast, and restrictors, then generate entry_list.ini from that sheet.

Working with Mod Cars in Assetto Corsa Mod Servers

For Assetto Corsa mod servers, MODEL and SKIN must match your folder tree exactly.

• MODEL → car folder under content\cars\
  • Example: content\cars\rss_gtm_lan → MODEL=rss_gtm_lan
• SKIN → skin folder under content\cars\<car>\skins\
  • Example: content\cars\rss_gtm_lan\skins\blue_77 → SKIN=blue_77

All players need the same mod and version as the server. Any mismatch leads to checksum errors or crashes.

Ready-Made entry_list Templates

Public open server

[SERVER]

LOCKED_ENTRY_LIST=0

[CAR_0]

MODEL=ks_bmw_m3_e30

SKIN=red

SPECTATOR_MODE=0

Minimal config. GUIDs empty. Drivers pick cars freely within the allowed list.

Private league grid

[SERVER]

LOCKED_ENTRY_LIST=1

[CAR_0]

DRIVERNAME=Driver One

TEAM=Team A

MODEL=ks_porsche_911_gt3_r

SKIN=01_white

GUID=7656119XXXXXXXXXX

BALLAST=0

RESTRICTOR=0

[CAR_1]

DRIVERNAME=Driver Two

TEAM=Team B

MODEL=ks_porsche_911_gt3_r

SKIN=02_black

GUID=7656119YYYYYYYYYY

BALLAST=20

RESTRICTOR=0

One block per driver, fixed skins, ballast per driver.

One-make or spec series

• Same MODEL for every CAR_x.
• Different SKIN and GUID.
• Optional fixed BALLAST for the whole field.

Store these templates in a separate folder so you can drop them into new servers in seconds.

Content Manager Server Workflow – The Easiest Way to Host Assetto Corsa Servers

Content Manager (full version) turns server setup into a workflow based on presets. You click, save, and deploy instead of editing .ini files by hand.

Enabling the Server Tab

• Open Content Manager.
• Go to Settings → Content Manager → Appearance.
• Check the Server box.

You will see a Server tab at the top. That tab is where you build and save all server presets.

Building Race and Freeroam Presets

In the Server tab you usually create two preset types:

• Race preset
  • Track and layout
  • Practice / qualify / race order
  • Time, weather, assists, damage
  • Car list and skins
• Freeroam preset
  • Freeroam map (for example Shutoko)
  • Single long practice session
  • Lower damage
  • Traffic cars flagged as AI in your entry list

Save each preset with a clear name like EU_GT3_SPA_RACE or Traffic_Shutoko_Night.

Packing and Uploading Presets

When a preset works:

1. Open the Server tab.
2. Select the preset.
3. Click Pack and choose a folder (for example, C:\AC_Servers\spa_gt3_server).

CM will generate:

• server_cfg.ini and entry_list.ini
• A ready-to-run server folder (with content if you enabled that option)

For a VPS or dedicated server:

• Zip the folder, upload it (SFTP or file manager), then unpack it into the server’s install path.

Many game panels also let you upload these files and use them as the base config.

Local Testing Before You Go Public

Always test locally first:

• Start the server from CM or by running acServer.exe in the packed folder.
• Watch the console for missing content, port errors, or lobby issues.
• In Content Manager or the base client, go to Drive → Online → LAN and join your own server.

Confirm that:

• The track and layout are correct
• The car list matches your preset
• Weather, time, and rules behave as expected

Once that looks solid, you can safely expose the server to friends or the public.

Quick Networking and Performance Guide for Assetto Corsa Servers

Networking Basics: Ports, Firewall, and VPNs

Assetto Corsa servers usually rely on 9600 for game traffic and 8081 for lobby or HTTP-related traffic, but do not assume only one protocol is enough. In practical setups, you should usually open 9600 on UDP and TCP, and treat 8081 as a port that may also need both UDP and TCP depending on your tooling.

On any host:

• Open these ports in your OS firewall
• Make sure no other service uses them
• On home routers, forward them from WAN to your server’s local IP

Common mistakes:

• Forwarding the wrong IP because DHCP changed it
• Forgetting the OS firewall while fixing the router
• Putting the PC in a DMZ instead of forwarding just the needed ports

If you cannot forward ports at home, you can share a VPN mesh (Hamachi, ZeroTier, Tailscale) with trusted friends and host a LAN server inside that virtual network. That is fine for small, closed groups, not for public high-player servers.

Performance and Running Multiple Servers

Send interval is one of the settings that affects how smooth other cars look. Higher values can improve multiplayer feel, but they also increase bandwidth use and can create connection issues if you push them too high.

Simple guidance:

• Low-end host: stay conservative, keep one server and fewer players
• Mid-range VPS: one main server, careful with plugins
• Strong RedSwitches hardware: several servers or one big traffic server with headroom

Watch:

• CPU spikes to 100% during full grids or AI traffic
• RAM creeping up when you stack mods and plugins
• Network graphs hitting upload caps when more players join

When you want several servers on one box:

• Give each server its own UDP, TCP, and HTTP port
• Use separate folders per instance
• Reserve CPU and RAM for each in your planning, even if you do not hard-pin cores yet

When Free Hosting Starts to Hurt

Free home hosting works until:

• Players complain about lag even on small grids
• Router reboots and power cuts kill sessions
• You cannot run more than one server cleanly
• You feel nervous about ports open on your home IP

At that point, stop patching the same old PC. Move the setup to a VPS or dedicated server:

• VPS if you want one lean race server
• RedSwitches dedicated server if you want traffic, big grids, or several servers on one machine

Copy your configs and content across once, then treat the home box as a test bench only.

Fast Troubleshooting Checklist

When something breaks, run through this list:

• Server not in lobby
  • Check REGISTER_TO_LOBBY=1
  • Confirm ports are open and not in use
  • Watch the server console for lobby errors
• Checksum or content mismatch
  • Make sure clients and server share the same cars and tracks
  • Repack mod bundles and version them clearly
• Players stuck on join or crashes on join
  • Check pit box count vs max clients
  • Test with stock content only
• High ping and rubber-banding
  • Watch upload usage during full grids
  • Lower player count or tick rate
  • Move from home or a weak VPS to stronger hardware like a RedSwitches server

Final Thoughts

You now have everything you need to plan hardware, pick an OS, install the tools, and run stable Assetto Corsa servers without guessing. Start small, test on LAN, fix your configs, then open the doors to friends or the public once you trust your setup. 

When your player count grows, or traffic and multiple instances start to choke a home PC or small VPS, treat that as a signal, not a surprise. 

Move your stack to RedSwitches bare metal server, map your presets to a dedicated box, and let your community race or cruise on hardware built to stay online.

FAQs

Q. Can I keep Assetto Corsa server hosting free on an old PC?

Yes, as long as the PC is stable, has an SSD, and at least a few Mbps of upload, you can host small sessions for friends for free. Expect it to handle around 4–8 players with light mods. Once you see high CPU usage, stutters, or complaints about lag, it is time to move off that box.

Q. How many players can a single Assetto Corsa dedicated server handle?

Player count depends more on track pit count, CPU headroom, mod load, and upload quality than on a single universal number. Start with small tests, watch CPU and network usage, and scale up gradually. As a hard rule, never set MAX_CLIENTS higher than the track’s number of pits.

Q. Is Windows or Assetto Corsa’s dedicated server Linux better long term?

Windows is the easiest place to start because the official dedicated server is distributed as a Windows Steam Tool and works naturally with Content Manager. Linux makes more sense when you want Wine-based automation for the official DS or native AssettoServer for freeroam setups. A common path is: start on Windows, learn the basics, then move your stable configs to Linux when you want more control.

Q. Is it safe to expose ports for home hosting?

Opening only the game ports (like 9600 and 8081) on your router is reasonably safe if your OS is patched, the firewall is on, and you do not expose RDP or SSH to the internet. Never dump the PC into a DMZ and never forward broad port ranges “just to make it work.” If you feel uneasy about exposing your home IP, use a VPS or dedicated server and keep your house off the public map.

Q. Do all players need the same mods on Assetto Corsa mod servers?

Yes, for any modded car or track that the server uses, every player must have the same mod and the same version. If files differ, they will hit checksum kicks or crash on join. Extra apps or HUD elements are often optional, but core cars, tracks, and physics files must match the server exactly.

Q. Can I run Assetto Corsa and other games on the same RedSwitches server?

Yes, as long as you size the CPU, RAM, and bandwidth for all the servers you plan to run. Keep each game in its own folder or container, assign separate ports, and avoid scheduling big events for multiple titles at the same time. With a strong RedSwitches dedicated server, it is normal to host several game servers side by side.