08
Dec
2014

Insurgency Dedicated Linux Server Tutorial

Insurgency is a new tactical FPS game that runs on the Source engine and it proves to be very tactical and a difficult, unforgiving game. This means it has potential to be cross platform, and indeed there are server clients for Windows and Linux for multiplayer action, which I highly recommend to get the most out of the game.

Here I will describe the steps that need to be taken to install the server on a Linux-based system (E.g. Ubuntu). Firstly, you need at least 15GB or so free disk space for the server files. Then you need to download the Steam client for the server using the following commands:

apt-get update
apt-get upgrade
apt-get install ia32-libs
apt-get install screen
apt-get install nano

mkdir steamgames
cd steamgames
wget http://media.steampowered.com/installersteamcmd_linux.tar.gz
tar xvfz steamcmd_linux.tar.gz
./steamcmd.sh
login anonymous
force_install_dir ./insurgency/
app_update 237410 validate

Wait for the server to download (this could take a while depending on your internet connection). The files will all be validated after the main download has finished to ensure that there are no corrupted files. Once you’re dropped back at the steam command line, just type “exit”.

Now you need to configure the server. Head over to this site, which will allow you to easily create a server.cfg with all your settings. Save this file inside the cfg folder in the insurgency installation directory (you might need to go to /insurgency/insurgency to find the folder).

The last file that needs to be created is the startup script:

touch start.sh
chmod 744 start.sh

Now edit the file and enter the following details:

screen -d -m -S ins ./srcds_linux -console -IP xxx.xxx.xxx.xxx -port 27015 +servercfgfile ‘server.cfg’ +map ministry_coop

Enter your IP address (the local 192.168.x.x seems to work fine for me) and then save and close the file. This, when ran, will create a detached screen process which won’t show any output until you connect to the screen using screen -r. You can close the terminal session once you’ve ran it, because the screen will keep the servers output alive.

The last thing you need to do is forward the ports 27015-27030 to allow the server to communicate properly with clients. You can find guides online of how to do this, just Google your router model and look for instructions on forwarding ports (most likely done through the admin page, eg 192.168.0.1). If you are using this as a LAN-only server, you don’t need to do this.

Now you can run the server and connect to it in the server browser. Happy gaming!

Internet Speeds: WiFi vs Ethernet
Intel NUC DN2820FYKH Geekbench Problem

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.