This guide walks you through hosting a multiplayer server for Euro Truck Simulator 2 (ETS2) using the official dedicated server tool provided by SCS Software. You’ll set up a server on your own PC or a rented machine, configure it for you and your friends, and get it running with the correct ports and settings. No prior server experience is needed, but you should be comfortable editing text files and forwarding ports on your router.
What You’ll Need
- A copy of Euro Truck Simulator 2 on Steam (the server files are free, but the game is required to generate the initial configuration).
- A Windows or Linux machine that can run the server (the same PC you play on works for small groups).
- At least 4 GB of free RAM and a dual-core CPU (more for larger convoys).
- Administrator access to your router if you want friends outside your local network to join.
- The Steam client installed (for downloading the dedicated server tool).
Step-by-Step
- Install the Dedicated Server Tool – Open Steam, go to Library, and switch the filter from “Games” to “Tools”. Find “Euro Truck Simulator 2 Dedicated Server” and install it. It will appear in your Steam Library under Tools.
- Generate the Server Configuration – Run the dedicated server once from Steam. It will create a folder named
server_packagein your Documents directory (on Windows:Documents\Euro Truck Simulator 2 Dedicated Server). Inside, you’ll findserver_config.siiand aserver_package.siifile. - Edit the Server Configuration – Open
server_config.siiwith Notepad or any text editor. Set theserver_nameto something recognizable, choose aserver_password(leave empty for an open server), and setmax_playersto your desired limit (the default is 8, but you can raise it up to 128). Save the file. - Edit the Server Package – Open
server_package.sii. This file defines what map and mods the server uses. For a vanilla server, leave it as is. If you want to use mods, you’ll need to list them here (see Tips below). Save the file. - Run the Server – Launch “Euro Truck Simulator 2 Dedicated Server” from Steam again. A console window will open showing the server starting. Wait until you see a message like “Server is ready” or “Listening on port 27015”.
- Test Locally – Start ETS2 on your gaming PC, go to Multiplayer, and select “Connect to Server”. Enter
127.0.0.1as the address (orlocalhost) and the port (default 27015). If you can join, the server is working. - Port Forward (for friends outside your network) – Log into your router’s admin panel (usually at 192.168.1.1 or 192.168.0.1). Find the Port Forwarding section and create a new rule: forward UDP and TCP port
27015to the local IP address of the machine running the server. Also forward TCP port27016(used for querying). Save the rule. - Find Your Public IP – Visit a site like whatismyip.com to see your public IP address. Share this IP with friends, along with the port if it’s not the default. They will enter it in the “Connect to Server” box in ETS2.
- Keep the Server Running – The server runs as long as the console window is open. To run it in the background, you can use a tool like NSSM (Non-Sucking Service Manager) on Windows, or a systemd service on Linux. For simple use, just leave the console window open.
Common Mistakes
- Forgetting to forward both TCP and UDP – ETS2 uses both protocols. If you only forward UDP, the server may be visible but connections will fail.
- Using the wrong local IP – When forwarding ports, you must use the server machine’s static local IP (e.g., 192.168.1.50), not your public IP or a dynamic IP that changes.
- Not editing server_package.sii – If you add mods to the game but don’t list them in the server package file, the server will ignore them and clients will get a mismatch error.
- Setting max_players too high – A server with 128 players on a typical home connection will lag badly. Start with 8–16 and increase only if your bandwidth and CPU handle it.
- Leaving the server password empty unintentionally – If you want a private server, set a password. An empty password means anyone can join.
Tips
- Use a static IP for the server machine – Set a static local IP in your router’s DHCP reservation so the port forwarding rule always points to the right device.
- Back up your server files – Copy the
server_packagefolder before making major changes. This lets you revert quickly if something breaks. - Mods need to be on the server and all clients – For a modded server, every player must have the same mods installed and enabled. The server will enforce this.
- Run the server on a separate machine if possible – Hosting on the same PC you play on can cause stutters. If you have an old laptop, use it as a dedicated server.
- Check the server log – The console window shows errors and connection attempts. If someone can’t connect, ask them to try again while you watch the log for clues.
Troubleshooting
Server doesn’t start – Check that you have the latest version of the dedicated server tool. Also ensure your firewall isn’t blocking the executable. On Windows, allow it through Windows Defender Firewall when prompted, or manually add an inbound rule for ports 27015 and 27016.
Friends can’t connect – First, test locally. If that works, the issue is likely port forwarding. Double-check the rule, make sure the server machine’s IP hasn’t changed, and confirm your ISP isn’t blocking incoming connections (some residential ISPs do). You can also try using a VPN like Hamachi or Radmin VPN as a workaround.
Server is visible but joining fails – This usually means a mod mismatch. Ensure all players have the same mods and that the server_package.sii lists them correctly. Also check that the server version matches the game version (update both).
High ping or lag – Reduce max_players, close bandwidth-heavy applications on the server machine, and ensure the server is on a wired connection, not Wi-Fi.
Server crashes on map load – If you’re using mods, one of them may be incompatible. Remove mods one by one to isolate the culprit. Also check that the map mod is compatible with the server version.
Frequently Asked Questions
Q: Can I host a server without owning ETS2? – No, you need the game to generate the server configuration and to test the server, though the dedicated server tool itself is free.
Q: How many players can join? – The default is 8, but you can set up to 128 in the config. Realistically, a home connection can handle 10–20 players smoothly.
Q: Do all players need the same DLC? – No, but if the server uses DLC content (like map expansions), players without that DLC may not be able to join or may see missing areas. It’s best to require the same DLC for a seamless experience.
Q: Can I run the server on Linux? – Yes, SCS provides a Linux dedicated server. The setup is similar, but you’ll need to edit config files with a text editor and run the binary from the terminal.
Q: How do I change the server map? – Edit server_package.sii to point to a different map mod. You’ll need to download the map mod and place it in the server’s mod folder, then list it in the package file.
Q: Why does the server say “No connection” to the Steam backend? – This is normal if the server can’t reach Steam’s servers. Ensure the machine has internet access and that Steam isn’t blocked by a firewall. The server can still run locally without Steam connectivity.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Samsung Smart Speaker Rollable Display: Facts
- HP 9730e: Wide Prints, Not A3 Scans
- What 8888 Does When You Use It as DNS Server
- Credential Manager: Seamless Sign-In Explained
- API Governance for Public Data: What Growing Portfolios Need
- Enterprise AI Hidden Cost: Data Architecture ROI