Troubleshooting Assetto Corsa Server Issues

This guide covers the most common problems you'll run into running an Assetto Corsa dedicated server, from checksum errors to servers that won't start. Find your issue below.

Checksum Errors When Joining

Checksum errors happen when a client's local copy of a track or car doesn't match the version installed on the server. Both need to be identical, down to the source and version.

• Confirm the folder names in TRACK and CARS in cfg/server_cfg.ini exactly match the folder names uploaded to content/tracks/ and content/cars/.
• If you recently updated a mod on the server, every player needs to update to the same version before reconnecting.
• Share the exact download link for any custom content with your players so everyone has a matching copy.

Track or Car Not Found — Server Fails to Start

If the server refuses to start with an error about a missing track or car, the configuration is pointing at content that doesn't exist on disk.

• Check that TRACK and CARS in cfg/server_cfg.ini exactly match the folder names inside content/tracks/ and content/cars/. Folder names are case-sensitive.
• For tracks with layout variants, confirm CONFIG_TRACK matches the exact subfolder name. Leave it blank if the track has no variants.
• Check the Console tab for the specific error message. It will usually name the missing file or folder directly.

Start Your Assetto Corsa ServerUnlimited RAM · Unlimited slots · From $9.99/monthStart My Server

entry_list.ini Slot Count Errors

The number of [CAR_N] blocks in cfg/entry_list.ini must be equal to or greater than the MAX_CLIENTS value in cfg/server_cfg.ini, or the server will fail to start.

• Count the [CAR_N] blocks in your entry list, starting from [CAR_0], and compare that count to MAX_CLIENTS.
• Add more blocks if needed. Each one requires at minimum a MODEL and SKIN value:

[CAR_4]
MODEL=ks_ferrari_f40
SKIN=0_red
SPECTATOR_MODE=0
DRIVERNAME=
TEAM=
GUID=
BALLAST=0

Server Shows as Full or Players Can't Join

• Check that MAX_CLIENTS matches the number of open, non-spectator slots in entry_list.ini.
• If IS_OPEN=0 is set on a session (for example [RACE]), players can't join once that session has started. Change it to 1 to allow mid-session joins.
• If the server just restarted, it can take a few minutes to re-register with the public lobby. Try connecting by direct IP to confirm the server itself is accepting connections.

Port and Connection Issues

• Confirm UDP_PORT, TCP_PORT, and HTTP_PORT in cfg/server_cfg.ini match the ports assigned to your server on the Network tab in your MintServers panel. Mismatched ports will block connections.
• When connecting by direct IP, use the exact IP and port shown on the Network tab.

Server Not Appearing in the Public Browser

• Verify REGISTER_TO_LOBBY=1 is set in cfg/server_cfg.ini. If it's set to 0, the server stays private and won't show up in the public list.
• It can take a few minutes for a newly started server to appear in the browser. Try a direct IP connection first to confirm the server is actually running.
• Check the Console tab for any lobby registration errors.

Still stuck after working through the list above? No worries! Just open a support ticket with your server name, the exact error message, and any recent changes you made to your config files, and our team will gladly take a look.