Euro Truck Simulator 2 Server Hosting

What is the ETS2 Convoy dedicated server?

The ETS2 Convoy dedicated server is an SCS Software tool that hosts a session of Convoy, Euro Truck Simulator 2’s official multiplayer mode, independently of any player’s PC. In a normal Convoy session the session closes when the host leaves; with a dedicated server it stays open, and drivers can connect whenever they like to keep hauling cargo on the same map.

The tool is designed for virtual trucking companies (VTCs), Discord communities that run regular convoy events and groups of friends. SCS also offers an American Truck Simulator version of the same tool as a separate app; the two games need separate servers.

A common point of confusion is TruckersMP. TruckersMP is a third-party multiplayer mod independent of SCS, and its servers are run by its own team; you cannot rent and run your own TruckersMP server. ETS2 server hosting means hosting your own session on the game’s official Convoy infrastructure.

Which operating systems does the ETS2 server run on?

According to SCS’s official documentation, the ETS2 dedicated server runs on both Windows and Linux. The server does not require owning the game; it can be downloaded from the Tools section of your Steam library or via SteamCMD with app ID 1948160.

steamcmd +login anonymous +app_update 1948160 validate +quit

The only thing to watch on Linux is that the server needs the steamclient.so library to talk to Steam. The bundled server_launch.sh script sets this up; if you do not use the script, you need to create a symbolic link to the library. On Windows the server can be started from the Steam library or directly from the executable.

Which system should you choose? A Linux distribution such as Ubuntu 24.04 LTS uses less memory and makes it easy to manage the server as a systemd service. Windows Server is a familiar environment for those who want to manage files by drag and drop and copy them from a local game folder. The version installed with SteamCMD does not update itself; when a game patch arrives you have to run the update.

What are server_packages files and how do you create them?

server_packages.sii and server_packages.dat are two files exported from the game client that define which map, DLC and mod combination the server uses. The server will not start without them; on the other hand, it does not need the DLC or mod files themselves.

Steps to create the files:

1. In the game’s config.cfg, set g_console to 1.
2. Start the game with the DLC and mod selection you want on the server, load a profile and enter the map; the command only works with a map loaded.
3. Open the console with ~ and type export_server_packages.
4. Take the two generated files from the game’s user folder and copy them to the server’s root directory.

These files are not tied to your account; they only reflect the DLC and mod configuration. Every driver joining the server must have the same DLC and mod set, otherwise they cannot connect. When you change the DLC or mod list, export the files again and upload them to the server. Regenerating the packages after a major game update also prevents version mismatch errors.

How do you get a Steam login token for an ETS2 server?

A Steam login token for an ETS2 server is created on the Steam community’s game server account management page by entering the game’s app ID, and it is written into the server_logon_token field in server_config.sii. The SCS documentation states that the token must be generated with the game’s app ID (227300 for ETS2), not the server’s, and that you must own the game to get one.

Why the token matters: without it the server starts with an anonymous account and receives a non-persistent identity. The session’s search ID can then change on every restart, so the ID you announced to your community becomes invalid the next time it starts. With a token the server keeps a persistent identity and you can keep using the same details in VTC announcements.

Points to keep in mind:

• If you run several sessions on the same machine, each instance needs its own token and its own ports.
• The token is a credential; do not share it in screenshots or Discord channels.
• If you think the token has leaked, regenerate it on the same page and update the server file.

What settings are in server_config.sii?

server_config.sii is the main configuration file of an ETS2 server, holding the lobby name, description, password, player limit, ports, login token, moderators and game rules. It is created in the server’s root directory on first run.

Key options:

• lobby_name, description, welcome_message, password: the session’s visible details; the SCS documentation sets character limits for each (63 characters for the lobby name and password, for example).
• max_players: the player limit; the official default is 8.
• moderator_list: Steam IDs that automatically become moderators when they join.
• player_damage: whether players can damage each other.
• traffic: whether AI traffic is enabled.
• hide_in_company and hide_colliding: hide other players in company areas and when colliding.
• force_speed_limiter: makes the speed limiter mandatory for everyone.
• timezones: time zone behaviour.

During a session, moderators can set the time with /set_time and the rain with /set_rain_factor from chat; /help lists the commands. Moderators cannot be assigned while the session is running; restart the server for changes to apply.

Which ports does an ETS2 server use?

The ETS2 dedicated server uses two kinds of ports: physical ports that must be opened to the outside (by default 27015 for connections and 27016 for queries) and virtual ports used inside the Steam network that need no forwarding (by default 100 and 101).

The SCS documentation stresses that the server does not do NAT punching: for the session to be listed in the in-game browser it needs a public IP address and open ports. On a home connection you would have to fiddle with router settings, while on a VDS with a public IPv4 address you only need to add rules to the operating system firewall. For a second session on the same machine, move all physical and virtual ports to different values.

How many players can an ETS2 Convoy server hold?

SCS’s official dedicated server documentation gives 8 as both the default and the maximum for max_players. Community and some hosting guides describe larger convoys being tried by also raising g_max_convoy_size on the clients, but this is not listed as a supported configuration in the official documentation and requires every player to edit their own config file.

In practice this means:

• The standard, supported configuration is enough for convoys of up to eight.
• For larger VTC events, running several sessions in parallel (for example two separate eight-player convoys) is the supported route.
• If you experiment beyond eight, treat it as experimental; behaviour may change after updates.

The good news is that an ETS2 server is light on resources: physics and AI traffic are mostly calculated client-side, and the server mainly manages session state and synchronisation. So several Convoy sessions, or even an American Truck Simulator server, can comfortably run together on the same VDS. The table above shows estimated resources for these scenarios; disk use is mostly server files and logs.

Game server package or VDS for ETS2?

For ETS2 the page shows VDS packages; you can install the Convoy server on a VDS yourself or request a ready-made installation through a support ticket. Because the server is lightweight, a single virtual server can host several sessions, an ATS server and side services such as your VTC’s Discord bot.

What makes a VDS worthwhile for ETS2 communities:

• Public IP: you control the public address and ports the session needs to be listed in the browser.
• Multiple instances: with the -nosingle parameter you can open several sessions on the same machine, giving each its own -server_cfg file.
• Automation: set up scheduled tasks for updates, restarts and log cleanup.
• Dedicated resources: your cores are reserved for you, so neighbour load does not affect you during events.

If you will only run one small session, a smaller VPS can do the job; the choice depends on what else you plan to host on the machine. For a comparison of the two models see game server package or VDS?. For package capacities, rely on the current values in the package table on this page.

How do mods and DLC work on an ETS2 server?

The ETS2 dedicated server does not load mods and DLC directly; the server_packages files you export from the game define which content is used, and every player who joins must have the same content. According to the SCS documentation the server cannot access Steam Workshop and needs no extra DLC or mod data; uploading .scs mod files to the server folder changes nothing.

Recommended routine for a modded convoy:

1. Decide the mod list and load order your VTC will use and publish it in an announcements channel.
2. Start the game with that list, enter the map and export the packages.
3. Upload the files to the server and restart it.
4. Ask players to enable the same mods in the same order; sharing a Workshop collection makes this easier.

The same logic applies to map DLCs: if the package file includes a DLC map, players without that DLC cannot connect. For public sessions the base map gives the widest participation; for closed VTC sessions you can build the package around the community’s common DLC set. The mods_optioning option controls additional behaviour related to mod configuration flexibility.

How do you keep an ETS2 server secure and backed up?

ETS2 server security relies on protecting the password, moderator list and login token; backups rely on keeping the configuration and package files. Because Convoy stores map progress in players’ own profiles, there is no large world save to back up on the server side; what really matters is the configuration you put effort into.

• Use the password field for closed VTC sessions and change it regularly.
• Keep only trusted Steam IDs in moderator_list.
• Archive server_config.sii, server_packages.sii and server_packages.dat with a version note after every change.
• Protect remote access (SSH or remote desktop) with an IP restriction.

On the network side, the RouteFence firewall on LIONFIN infrastructure filters DDoS traffic at the network level and NOC and SOC teams monitor 24/7 (see our data center). Restarting the server and clearing logs before big events reduces the risk of unexpected outages during the event.

How do virtual trucking companies (VTCs) use an ETS2 server?

Virtual trucking companies use an ETS2 server to gather regular convoy events at a fixed address, enforce their rules from one place and give members a meeting point that is always open. Thanks to the persistent login token the session ID does not change, so the same details in Discord announcements stay valid for months.

A common setup on successful VTC servers:

• Two-tier sessions: a password-protected main session for members and a separate session for public showcase events, each with its own config file and ports.
• Event hours: restarting the server before large convoys and adjusting time and weather with moderator commands to suit the event.
• Rule set: keeping convoy discipline with settings such as a mandatory speed limiter, collision hiding and player damage turned off.
• Shared content list: keeping the DLC and mods in a fixed list and generating the package files from it.

In this setup a Discord bot, an event calendar or the company website often runs alongside the server. Keeping them all on the same VDS simplifies management, and the ETS2 server’s low resource use leaves room for such side services.

How do you update a VTC server and keep it online?

A community server’s reliability depends largely on update discipline; a version mismatch on event day is the complaint members raise most. Writing the maintenance steps down as a checklist and naming who is responsible is a good habit.

Installed via SteamCMD, the ETS2 server does not update itself; when a game patch ships, stop the server, run app_update 1948160 validate and, if needed, re-export the package files with the new game version. When the server and client versions do not match, players cannot join the session.

A maintenance flow that minimises downtime:

1. Follow SCS patch notes; major versions are usually announced as betas in advance.
2. On patch day, shut the server down cleanly with Ctrl+C and back up the config files.
3. Run the SteamCMD update.
4. Enter the map with the updated game, run export_server_packages again and upload the new files.
5. Start the server, confirm there are no errors in server.log.txt, then announce it to the community.

On Linux, defining the server as a systemd service restarts it automatically if the process exits unexpectedly; on Windows, Task Scheduler or a service wrapper does the same. This automatic restart is especially valuable against the known issue of the session closing when the Steam connection drops.

What are the most common ETS2 server errors?

The most frequent ETS2 server problems are missing or outdated package files, missing port forwarding and DLC or mod mismatches between player and server. The first place to look is server.log.txt in the server directory, and after a crash server.crash.txt.

• Server will not start: server_packages.sii and server_packages.dat are not in the server root, or the command was run without a map loaded.
• Session not listed: the physical ports are not open or the server is behind NAT; searching directly by search ID still works.
• Player cannot connect: the player’s DLC or mod set does not match the package file, or the game version differs.
• Search ID changes on every start: server_logon_token has not been set.
• Session closes with “[MP] Steam disconnected”: one of SCS’s known issues; the server lost its Steam connection. Set up an automatic restart with a watchdog script.

Use Ctrl+C in the console to stop the server; killing the process forcibly can leave logs incomplete.