<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://stationeers-wiki.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=95.27.42.27</id>
	<title>Stationeers Community Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://stationeers-wiki.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=95.27.42.27"/>
	<link rel="alternate" type="text/html" href="https://stationeers-wiki.com/Special:Contributions/95.27.42.27"/>
	<updated>2026-04-04T10:46:29Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.6</generator>
	<entry>
		<id>https://stationeers-wiki.com/index.php?title=SystemD_Server_Guide&amp;diff=15004</id>
		<title>SystemD Server Guide</title>
		<link rel="alternate" type="text/html" href="https://stationeers-wiki.com/index.php?title=SystemD_Server_Guide&amp;diff=15004"/>
		<updated>2023-04-12T08:53:58Z</updated>

		<summary type="html">&lt;p&gt;95.27.42.27: No need to edit this file manually. Furthermore, it&amp;#039;s not safe and error prone.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Tutorials]]&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
* A machine that runs any Linux distribution that uses SystemD&lt;br /&gt;
* Access to, and basic knowledge of your Linux shell&lt;br /&gt;
* &amp;lt;code&amp;gt;sudo&amp;lt;/code&amp;gt;-rights&lt;br /&gt;
* At least 16GB RAM&lt;br /&gt;
&lt;br /&gt;
== Preparing the server ==&lt;br /&gt;
To maximize server security, we will be setting up a dedicated user that only has the privileges to run the dedicated server, and nothing else.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;sudo useradd -m -s /sbin/nologin stationeers&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installing SteamCmd ==&lt;br /&gt;
Follow the instructions here to get SteamCmd installed: https://developer.valvesoftware.com/wiki/SteamCMD#Package_From_Repositories&lt;br /&gt;
&lt;br /&gt;
== Creating the SystemD service==&lt;br /&gt;
Now it&#039;s time to create the service-file for SystemD so we can use it to control starting and stopping the Stationeers server.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;sudo nano /etc/systemd/system/stationeers.service&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Paste the following into the editor:&lt;br /&gt;
----&lt;br /&gt;
&amp;lt;code&amp;gt;[Unit]&amp;lt;br&amp;gt;&lt;br /&gt;
Description=Stationeers Dedicated Server&amp;lt;br&amp;gt;&lt;br /&gt;
Wants=network-online.target&amp;lt;br&amp;gt;&lt;br /&gt;
After=syslog.target network.target nss-lookup.target network-online.target&lt;br /&gt;
&lt;br /&gt;
[Service]&amp;lt;br&amp;gt;&lt;br /&gt;
Environment=&amp;quot;LD_LIBRARY_PATH=./linux64&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
ExecStartPre=/usr/games/steamcmd +force_install_dir &amp;quot;/home/stationeers/StationeersDedicatedServer&amp;quot; +login anonymous +app_update 600760 validate +quit&amp;lt;br&amp;gt;&lt;br /&gt;
ExecStart=/home/stationeers/StationeersDedicatedServer/rocketstation_DedicatedServer.x86_64 -loadlatest &amp;quot;NAME_OF_SAVE&amp;quot; PLANET -difficulty DIFFICULTY_SETTING -settings StartLocalHost true ServerVisible true LocalIpAddress IP_ADDRESS ServerName &amp;quot;NAME_IN_SERVER_LIST&amp;quot; ServerPassword &amp;quot;YOUR_SECURE_PASSWORD&amp;quot; ServerMaxPlayers MAX_PLAYERS UPNPEnabled false&amp;lt;br&amp;gt;&lt;br /&gt;
User=stationeers&amp;lt;br&amp;gt;&lt;br /&gt;
Group=stationeers&amp;lt;br&amp;gt;&lt;br /&gt;
StandardOutput=journal&amp;lt;br&amp;gt;&lt;br /&gt;
Restart=on-failure&amp;lt;br&amp;gt;&lt;br /&gt;
WorkingDirectory=/home/stationeers&lt;br /&gt;
&lt;br /&gt;
[Install]&amp;lt;br&amp;gt;&lt;br /&gt;
WantedBy=multi-user.target&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
The stuff under &amp;lt;code&amp;gt;[Unit]&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;[Install]&amp;lt;/code&amp;gt; is just to name the service in Linux, and declare when it&#039;s safe to start. It&#039;s the stuff under &amp;lt;code&amp;gt;[Service]&amp;lt;/code&amp;gt; that is the &amp;quot;business end&amp;quot; of this file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ExecStartPre&amp;lt;/code&amp;gt; runs the &amp;lt;code&amp;gt;steamcmd&amp;lt;/code&amp;gt; application to update the dedicated server. You might want to check that &amp;lt;code&amp;gt;steamcmd&amp;lt;/code&amp;gt; is actually installed in /usr/games/ by running the following command: &amp;lt;code&amp;gt;find /usr/ -name &amp;quot;steamcmd&amp;quot;&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;ExecStart&amp;lt;/code&amp;gt; starts the Stationeers dedicated server. Be sure to replace all the UPPERCASE entries with what you want for your server. See here: https://github.com/rocket2guns/StationeersDedicatedServerGuide/blob/main/README.md&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;User&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;Group&amp;lt;/code&amp;gt; ensures that the dedicated server runs with the user we set up earlier.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;StandardOutput=journal&amp;lt;/code&amp;gt; directs all log-messages to the system journal. If something goes wrong, you don&#039;t have to locate any log-files, you just run the command &amp;lt;code&amp;gt;journalctl -fu stationeers&amp;lt;/code&amp;gt; to browse the journal for what the user &amp;lt;code&amp;gt;stationeers&amp;lt;/code&amp;gt; has output.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;Restart=on-failure&amp;lt;/code&amp;gt; ensures that if the server crashes, it will automatically restart.&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;WorkingDirectory=/home/stationeers&amp;lt;/code&amp;gt; makes sure that everything we do assumes that we&#039;re standing in this folder when we do it. It&#039;s kind of redundant here, but I keep it in for safety.&lt;br /&gt;
&lt;br /&gt;
== Wrapping it all up ==&lt;br /&gt;
Now that we&#039;ve created the service-file, we have to let SystemD know it&#039;s there. Run &amp;lt;code&amp;gt;sudo systemctl daemon-reload&amp;lt;/code&amp;gt; to do that. Any time you edit the service-file, you have to run this command to make SystemD aware of the changes you&#039;ve made.&lt;br /&gt;
&lt;br /&gt;
That&#039;s it! All we need to do now is run &amp;lt;code&amp;gt;sudo systemctl start stationeers&amp;lt;/code&amp;gt;, and it will download Stationeers Dedicated Server, start it with the parameters we&#039;ve set, and run until we either reboot the machine, or run &amp;lt;code&amp;gt;sudo systemctl stop stationeers&amp;lt;/code&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
If there&#039;s an update to Stationeers, just run &amp;lt;code&amp;gt;sudo systemctl restart stationeers&amp;lt;/code&amp;gt;, and the &amp;lt;code&amp;gt;ExecStartPre&amp;lt;/code&amp;gt; line in the service-file will ensure that &amp;lt;code&amp;gt;steamcmd&amp;lt;/code&amp;gt; downloads the latest version.&lt;br /&gt;
&lt;br /&gt;
Want the dedicated server to start with the machine every time you reboot? Just run &amp;lt;code&amp;gt;sudo systemctl enable stationeers&amp;lt;/code&amp;gt; to enable start-on-boot, and &amp;lt;code&amp;gt;sudo systemctl disable stationeers&amp;lt;/code&amp;gt; to disable it again.&lt;/div&gt;</summary>
		<author><name>95.27.42.27</name></author>
	</entry>
</feed>