User:Webb/New linux server: Difference between revisions
No edit summary |
No edit summary |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
:''This is | :''This article is based on a guide written by Raizo, the original of which can be found [https://blog.raizo.dev/posts/tf2-classic-linux-server-tutorial/ here].'' | ||
== Reading this article == | |||
<!-- Originally from https://wiki.teamfortress.com/wiki/Linux_dedicated_server#Reading_this_article --> | <!-- Originally from https://wiki.teamfortress.com/wiki/Linux_dedicated_server#Reading_this_article --> | ||
A command prefixed by <code>#</code> is meant to be run as '''root'''. | A command prefixed by <code>#</code> is meant to be run as '''root'''. | ||
| Line 22: | Line 11: | ||
Some commands are listed in-line with the rest of a paragraph and lack this symbol, in which case you should run the command as whichever account you're currently logged in with. | Some commands are listed in-line with the rest of a paragraph and lack this symbol, in which case you should run the command as whichever account you're currently logged in with. | ||
=== | == Prerequisites == | ||
* A Linux server running Ubuntu Server<sup>*</sup> on an x86_64 CPU<sup>**</sup> with root access | |||
* At least 20GB of free storage | |||
* A minimum of a 10Mbps upload speed if you intend on hosting a server over the Internet, more will be needed if you host custom content | |||
* An opened port on your firewall for the server | |||
* ''Optional'': An SSH/SFTP client if doing remote access/file management | |||
* ''Optional'': A port that's been forwarded for the server if you wish to have it accessible over the internet | |||
<sup>*</sup> This guide was written for and tested on Ubuntu Server 24.04 LTS Minimal. Other distros may use different package names and conventions. | |||
<sup>**</sup> Using an x86 compatibility layer like Box86 for another architecture is unsupported and may not work. | |||
== Preparing for install == | |||
=== Dependencies === | |||
We'll need to install some required packages and tools for our server to work, as well as for installation. | |||
Since the legacy TF2C branch, Source SDK, and SteamCMD are built for 32-bit, we'll need to enable 32-bit packages. We'll also add the <code>multiverse</code> repository which has SteamCMD. | |||
<pre> | <pre> | ||
| Line 44: | Line 38: | ||
</pre> | </pre> | ||
Next, we'll install the <code>dialog</code> package so the Steam Subscriber Agreement dialog works, and then the rest of the packages we need. | |||
<pre> | <pre> | ||
# apt install dialog | # apt install dialog | ||
# apt install steamcmd p7zip aria2 tilde lib32z1 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libcurl3-gnutls:i386 libsdl2-2.0-0:i386 wget | # apt install steamcmd p7zip aria2 tilde lib32z1 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libcurl3-gnutls:i386 libsdl2-2.0-0:i386 wget | ||
</pre> | </pre> | ||
If your version of Ubuntu doesn't come with a text editor, you may install one now. For this guide we'll use <code>nano</code>. | If your version of Ubuntu doesn't come with a text editor, you may install one now. For this guide we'll use <code>nano</code>. | ||
| Line 58: | Line 49: | ||
<pre># apt install nano</pre> | <pre># apt install nano</pre> | ||
Switch to the srcds user you | === Creating a user for the server === | ||
Pick a directory to install your server into. Many put it under a directory in <code>/opt</code>, but for this guide we'll be using <code>/home/srcds</code>. | |||
Create a disabled user with a home directory. | |||
<pre> | |||
# useradd -s /bin/false -mr srcds | |||
</pre> | |||
<code>-m</code> creates a home directory for the new user, <code>-r</code> specifies that it's a system account that will not have a password, and <code>-s /bin/false</code> prevents the account from having a default shell. | |||
=== Installing Source SDK Base 2013 Dedicated Server (SDK 2013) === | |||
Switch to the new <code>srcds</code> user you made, and run SteamCMD. | |||
<pre> | <pre> | ||
| Line 67: | Line 72: | ||
</pre> | </pre> | ||
You should be dropped into a SteamCMD shell. We can install the SDK now. Note that <code>force_install_dir</code> must be ran before <code>login anonymous</code>. | You should be dropped into a SteamCMD shell. We can install the SDK 2013 now. Note that <code>force_install_dir</code> must be ran before <code>login anonymous</code>. | ||
<pre> | <pre> | ||
| Line 77: | Line 82: | ||
If everything went well, <code>srcds</code> should be installed and you should be back at your user shell. | If everything went well, <code>srcds</code> should be installed and you should be back at your user shell. | ||
Before we continue we'll need to fix some files. | |||
Valve changed some shared object file names in the SDK, but the objects included with our install of SDK 2013 have not adopted the new names. | |||
Since these are simply renames, we can symlink them. | |||
'''Your server will not start without doing this.''' | '''Your server will not start without doing this.''' | ||
<pre> | <pre> | ||
| Line 111: | Line 101: | ||
$ ln -s vphysics_srv.so vphysics.so | $ ln -s vphysics_srv.so vphysics.so | ||
$ ln -s soundemittersystem_srv.so soundemittersystem.so | $ ln -s soundemittersystem_srv.so soundemittersystem.so | ||
</pre> | </pre> | ||
Finally, we'll also symlink <code>steamclient.so</code> to a special directory to prevent bugs. | |||
<pre> | <pre> | ||
$ mkdir -p ~/.steam/sdk32 | $ mkdir -p ~/.steam/sdk32 | ||
$ ln -s ~/sdk/bin/steamclient.so ~/.steam/sdk32/ | $ ln -s ~/sdk/bin/steamclient.so ~/.steam/sdk32/ | ||
</pre> | |||
== Installing TF2C == | |||
We'll be downloading the archived verison of TF2C, since it's unlikely to get updates. You have the option of using TF2CDownloader, but we won't cover it here. | |||
<pre> | |||
$ wget https://wiki.tf2classic.com/kachemak/tf2classic.zip -O /tmp/tf2classic.zip | |||
$ mkdir ~/sdk/tf2classic | |||
$ cd ~/sdk/tf2classic | |||
$ 7z x /tmp/tf2classic.zip && rm /tmp/tf2classic.zip | |||
</pre> | |||
This will download the latest archive, create its directory, and extract it. If extraction succeeds it will also delete the downloaded archive. | |||
We'll also need to do a quick symlink in TF2C's bin folder. | |||
<pre> | |||
$ cd ~/sdk/tf2classic/bin | |||
$ ln -s server.so server_srv.so | |||
</pre> | </pre> | ||
| Line 135: | Line 143: | ||
== Server Configuration == | == Server Configuration == | ||
For a basic, private server, you should only need to set a password in <code>sdk/tf2classic/cfg/server.cfg</code> by appending the file with <code>sv_password yourpassword</code>. | |||
You can also make it LAN-only by appending <code>sv_lan 1</code> in the same file. | |||
If you want a more complicated setup, consider using [https://cfg.tf/ cfg.tf]. If you don't need this you can skip to the next section. | |||
Make sure the server type is set to “Internet and LAN” if you want players outside your LAN to be able to join (you may need to port forward if you’re on consumer broadband or open ports on your firewall). | Make sure the server type is set to “Internet and LAN” if you want players outside your LAN to be able to join (you may need to port forward if you’re on consumer broadband or open ports on your firewall). | ||
Upload the generated ZIP file to your server using SFTP, unzip the folder | Upload the generated ZIP file to your server, perhaps using SFTP, and unzip the folder. | ||
<pre> | <pre> | ||
| Line 152: | Line 163: | ||
</pre> | </pre> | ||
== | == Managing the server via Systemd == | ||
Systemd is a program that will automatically handle things like logging, restarts, and starting your server when your machine boots. We'll use this to run our server, instead of manually running commands. | Systemd is a program that will automatically handle things like logging, restarts, and starting your server when your machine boots. We'll use this to run our server, instead of manually running commands. | ||
| Line 158: | Line 169: | ||
=== Creating an SDK 2013 update script === | === Creating an SDK 2013 update script === | ||
We're going to create a script that will update | We're going to create a script that will update SDK 2013 for us instead of typing it out manually each time. Later, we'll optionally use this script to check and update SDK 2013 on our server automatically when the server starts. | ||
First, let's create a directory for the script. | First, let's create a directory for the script. | ||
| Line 187: | Line 198: | ||
=== Creating a service file === | === Creating a service file === | ||
Create a service file in <code>/etc/systemd/system/</code> as root. | Create a service file in <code>/etc/systemd/system/</code> as root. For this guide we'll use <code>/etc/systemd/system/tf2c.service</code>. | ||
<pre> | <pre> | ||
[Unit] | [Unit] | ||
Description=TF2C | Description=TF2C Server | ||
After=network-online.target | After=network-online.target | ||
Wants=network-online.target | Wants=network-online.target | ||
| Line 208: | Line 218: | ||
TimeoutStartSec=infinity | TimeoutStartSec=infinity | ||
Restart=always | Restart=always | ||
[Install] | [Install] | ||
| Line 216: | Line 223: | ||
</pre> | </pre> | ||
Then, enable the service to start with Systemd. | Then, enable the service to start with Systemd on boot. | ||
<pre> | <pre> | ||
# systemctl enable tf2c.service | # systemctl enable tf2c.service | ||
</pre> | </pre> | ||
You may create as many services as you have TF2C servers but remember to name the service files uniquely. When modifying service files, remember to run <code>systemctl daemon-reload</code> before restarting the service. | |||
=== Automatic restarts using crontab === | === Automatic restarts using crontab === | ||
As root, execute <code>crontab -e</code>. This will open a special file where you can | Cron is a program built into most Linux distros that runs scheduled commands. | ||
As root, execute <code>crontab -e</code>. This will open a special file in your editor where you can declare what jobs you want to run and when. Let's add a job to run at 04:00 that will restart our server. | |||
<pre> | <pre> | ||
| Line 230: | Line 241: | ||
</pre> | </pre> | ||
=== Manually managing services === | |||
=== | |||
If you don't wish to use the service files above to automatically boot servers, or you need to perform these actions for maintenance: you may issue commands to manually ''start'', ''stop'', ''restart'', or ''update'' the server(s) through systemd. | If you don't wish to use the service files above to automatically boot servers, or you need to perform these actions for maintenance: you may issue commands to manually ''start'', ''stop'', ''restart'', or ''update'' the server(s) through systemd. | ||
Latest revision as of 15:55, 8 December 2025
- This article is based on a guide written by Raizo, the original of which can be found here.
Reading this article
A command prefixed by # is meant to be run as root.
A command prefixed by $ is meant to be run as a regular user without root permissions. In this case the srcds user.
A command prefixed by Steam> is meant to be run inside of a SteamCMD shell.
Some commands are listed in-line with the rest of a paragraph and lack this symbol, in which case you should run the command as whichever account you're currently logged in with.
Prerequisites
- A Linux server running Ubuntu Server* on an x86_64 CPU** with root access
- At least 20GB of free storage
- A minimum of a 10Mbps upload speed if you intend on hosting a server over the Internet, more will be needed if you host custom content
- An opened port on your firewall for the server
- Optional: An SSH/SFTP client if doing remote access/file management
- Optional: A port that's been forwarded for the server if you wish to have it accessible over the internet
* This guide was written for and tested on Ubuntu Server 24.04 LTS Minimal. Other distros may use different package names and conventions.
** Using an x86 compatibility layer like Box86 for another architecture is unsupported and may not work.
Preparing for install
Dependencies
We'll need to install some required packages and tools for our server to work, as well as for installation.
Since the legacy TF2C branch, Source SDK, and SteamCMD are built for 32-bit, we'll need to enable 32-bit packages. We'll also add the multiverse repository which has SteamCMD.
# add-apt-repository multiverse # dpkg --add-architecture i386 # apt update
Next, we'll install the dialog package so the Steam Subscriber Agreement dialog works, and then the rest of the packages we need.
# apt install dialog # apt install steamcmd p7zip aria2 tilde lib32z1 libbz2-1.0:i386 lib32gcc-s1 lib32stdc++6 libcurl3-gnutls:i386 libsdl2-2.0-0:i386 wget
If your version of Ubuntu doesn't come with a text editor, you may install one now. For this guide we'll use nano.
# apt install nano
Creating a user for the server
Pick a directory to install your server into. Many put it under a directory in /opt, but for this guide we'll be using /home/srcds.
Create a disabled user with a home directory.
# useradd -s /bin/false -mr srcds
-m creates a home directory for the new user, -r specifies that it's a system account that will not have a password, and -s /bin/false prevents the account from having a default shell.
Installing Source SDK Base 2013 Dedicated Server (SDK 2013)
Switch to the new srcds user you made, and run SteamCMD.
# sudo -Hu srcds bash $ cd ~ $ . /etc/environment $ steamcmd
You should be dropped into a SteamCMD shell. We can install the SDK 2013 now. Note that force_install_dir must be ran before login anonymous.
Steam>force_install_dir /home/srcds/sdk Steam>login anonymous Steam>app_update 244310 -beta previous2021 Steam>quit
If everything went well, srcds should be installed and you should be back at your user shell.
Before we continue we'll need to fix some files.
Valve changed some shared object file names in the SDK, but the objects included with our install of SDK 2013 have not adopted the new names. Since these are simply renames, we can symlink them.
Your server will not start without doing this.
$ cd ~/sdk/bin $ ln -s datacache_srv.so datacache.so $ ln -s dedicated_srv.so dedicated.so $ ln -s engine_srv.so engine.so $ ln -s materialsystem_srv.so materialsystem.so $ ln -s replay_srv.so replay.so $ ln -s scenefilecache_srv.so scenefilecache.so $ ln -s shaderapiempty_srv.so shaderapiempty.so $ ln -s studiorender_srv.so studiorender.so $ ln -s vphysics_srv.so vphysics.so $ ln -s soundemittersystem_srv.so soundemittersystem.so
Finally, we'll also symlink steamclient.so to a special directory to prevent bugs.
$ mkdir -p ~/.steam/sdk32 $ ln -s ~/sdk/bin/steamclient.so ~/.steam/sdk32/
Installing TF2C
We'll be downloading the archived verison of TF2C, since it's unlikely to get updates. You have the option of using TF2CDownloader, but we won't cover it here.
$ wget https://wiki.tf2classic.com/kachemak/tf2classic.zip -O /tmp/tf2classic.zip $ mkdir ~/sdk/tf2classic $ cd ~/sdk/tf2classic $ 7z x /tmp/tf2classic.zip && rm /tmp/tf2classic.zip
This will download the latest archive, create its directory, and extract it. If extraction succeeds it will also delete the downloaded archive.
We'll also need to do a quick symlink in TF2C's bin folder.
$ cd ~/sdk/tf2classic/bin $ ln -s server.so server_srv.so
Testing the server
Before proceeding, we can manually run the server to make sure the install was successful.
$ cd ~/sdk $ ./srcds_run -game tf2classic +map ctf_2fort +sv_password changethis
If all goes well, it should start.
Server Configuration
For a basic, private server, you should only need to set a password in sdk/tf2classic/cfg/server.cfg by appending the file with sv_password yourpassword.
You can also make it LAN-only by appending sv_lan 1 in the same file.
If you want a more complicated setup, consider using cfg.tf. If you don't need this you can skip to the next section.
Make sure the server type is set to “Internet and LAN” if you want players outside your LAN to be able to join (you may need to port forward if you’re on consumer broadband or open ports on your firewall).
Upload the generated ZIP file to your server, perhaps using SFTP, and unzip the folder.
$ cd /tmp $ unzip $PATH_TO_ARCHIVE
And merge the cfg folder with /home/srcds/sdk/tf2classic/cfg/.
$ rsync /tmp/cfg ~/srcds/sdk/tf2classic/cfg $ rm -rf /tmp/cfg
Managing the server via Systemd
Systemd is a program that will automatically handle things like logging, restarts, and starting your server when your machine boots. We'll use this to run our server, instead of manually running commands.
Creating an SDK 2013 update script
We're going to create a script that will update SDK 2013 for us instead of typing it out manually each time. Later, we'll optionally use this script to check and update SDK 2013 on our server automatically when the server starts.
First, let's create a directory for the script.
$ mkdir ~/bin $ nano ~/bin/update-sdk.steamcmd
Fill the file with the following contents:
@ShutdownOnFailedCommand 1 //set to 0 if updating multiple servers at once @NoPromptForPassword 1 force_install_dir /home/srcds/sdk login anonymous app_update 244310 -beta previous2021 quit
You can execute this script manually by using the +runscript argument on SteamCMD.
$ . /etc/environment $ steamcmd +runscript /home/srcds/bin/update-sdk.steamcmd
Creating a service file
Create a service file in /etc/systemd/system/ as root. For this guide we'll use /etc/systemd/system/tf2c.service.
[Unit] Description=TF2C Server After=network-online.target Wants=network-online.target [Service] Type=simple User=srcds StandardError=journal StandardOutput=journal WorkingDirectory=/home/srcds/sdk RemainAfterExit=no ExecStartPre=/usr/games/steamcmd +runscript /home/srcds/bin/update-sdk.steamcmd # Exclude or comment this if you don't want to check for an update on each restart Environment="LD_LIBRARY_PATH=".:bin:$LD_LIBRARY_PATH"" ExecStart=/usr/bin/script -e -c "/home/srcds/sdk/srcds_linux +map ctf_2fort -game tf2classic +maxplayers 24" /dev/null TimeoutStartSec=infinity Restart=always [Install] WantedBy=multi-user.target
Then, enable the service to start with Systemd on boot.
# systemctl enable tf2c.service
You may create as many services as you have TF2C servers but remember to name the service files uniquely. When modifying service files, remember to run systemctl daemon-reload before restarting the service.
Automatic restarts using crontab
Cron is a program built into most Linux distros that runs scheduled commands.
As root, execute crontab -e. This will open a special file in your editor where you can declare what jobs you want to run and when. Let's add a job to run at 04:00 that will restart our server.
0 4 * * * systemctl restart tf2c.service
Manually managing services
If you don't wish to use the service files above to automatically boot servers, or you need to perform these actions for maintenance: you may issue commands to manually start, stop, restart, or update the server(s) through systemd.
# systemctl restart tf2c # in case you need to restart manually or to grab updates!! # systemctl stop tf2c # in case you need to stop the server manually # systemctl start tf2c # in case you need to start the server manually # systemctl disable tf2c # in case you need to stop the server from booting as your system initializes # systemctl enable tf2c # in case you need to start the server to boot as your system initializes
See also Dedicated Linux Server Extras.