This guide covers common issues and solutions for Assetto Corsa dedicated servers hosted with Legion Hosting. For initial server setup, see the Assetto Corsa Server Setup Guide.

Checksum Errors When Joining

Checksum errors occur when a client's local copy of a track or car does not match the version installed on the server. Both must be identical — the same mod version from the same source.

• Verify the track folder name in TRACK and the car folder names in CARS in cfg/server_cfg.ini exactly match the folder names uploaded to content/tracks/ and content/cars/ on the server.
• If you recently updated a mod on the server, all clients must also update to the same version before reconnecting.
• Share the exact download link for custom content with your players so everyone has the same version.
• Content Manager can detect mismatched content before a join attempt and display which files differ.

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 references content that does not exist on disk.

• Check that the folder names in cfg/server_cfg.ini (TRACK and CARS) 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 inside the track directory. If the track has no variants, leave CONFIG_TRACK empty.
• Check the GPanel console log for the specific error message — it will usually name the missing file or folder.

Missing Content Errors for Clients

Players must install the same custom tracks and cars locally before joining a server with custom content.

• Share the download source with your players so they can obtain matching versions of all custom content.
• Content Manager can detect missing content before a join attempt and display which files are needed.
• For more details on uploading custom content, see the Assetto Corsa: Custom Content Installation guide.

entry_list.ini Slot Count Error

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

• Count the [CAR_N] blocks in your entry_list.ini (they start at [CAR_0]) and compare to your MAX_CLIENTS value.
• Add additional blocks if needed. Each block requires at minimum MODEL and SKIN values. Example:

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

Server Shows as Full or Players Cannot Join

• Check that MAX_CLIENTS in cfg/server_cfg.ini matches the number of open (non-spectator) slots in cfg/entry_list.ini.
• If IS_OPEN=0 is set on a session section (e.g. [RACE]), players cannot join after the session has started. Change to IS_OPEN=1 to allow mid-session joins.
• If the server recently restarted, it may take a few minutes to re-register with the Kunos lobby. Try connecting via direct IP to confirm the server is accepting connections.

Port and Connection Issues

• Confirm the UDP_PORT, TCP_PORT, and HTTP_PORT values in cfg/server_cfg.ini match the ports assigned in your GPanel Network tab. Mismatched ports will prevent connections.
• When connecting via direct IP, use the IP and port shown in the GPanel Network tab.
• For more information on finding your server's IP and port, see the server IP and port guide.

Server Not Appearing in the Public Browser

• Verify that REGISTER_TO_LOBBY=1 is set in cfg/server_cfg.ini. If set to 0, the server will not appear in the public Kunos lobby.
• It can take several minutes for a newly started server to appear in the browser. Try connecting via direct IP first to confirm the server is running.
• Check the GPanel console log for lobby registration errors.

Related Articles

• Assetto Corsa: Server Setup Guide
• Assetto Corsa: Custom Content Installation (Tracks, Cars & Skins)
• How to Find Your Server IP and Port