Requirements
Ubuntu Server 18.04
4GB of RAM can be run with 2GB if you reboot 2-3 times a day.
2 vCPU can be run on 1 vCPU
50GB or More Storage


You should have your Ubuntu Server 18.04 up and running. I recommend a VPS or VM. Shoot grab an old computer with 4GB of RAM that you have in closet and put it to use.

NOTE: If you are running this on a VM at home. Will have to do some Port Forwarding for other players to connect. I recommend not forwarding the dashboard Port 51422 so it will only be accessible on our Network.

Applications: I recommend
Text editors
- Visual Studio Code https://code.visualstudio.com/download
- NotePad++ https://notepad-plus-plus.org/download/

Bitvise SSH client with SFTP built in. When you connect it will create a SFTP connection as well. Kinda of nice when you are moving files to and from the server.
- Btivise https://www.bitvise.com/ssh-client
or
Putty (SSH) and FileZilla (SFTP/FTP) if you are old school.


Connect via SSH and Log in.
An update command before we get started this will reboot the server as well.


Click yes if it ask for permission to restart services.



After the reboot log in and since we are root. We will install some tools to compile code.
NOTE: Bitvise will reconnect after reboot. Right Click the small icon on the task bar to open another Terminal Window.


Some Dependencies for Ruby 2.6.3


Dependency for Steam

I recommend copying and paste into Root Terminal Window. This is using SAW Default Ports. Change x.x.x.x to your Public IP



you may want to add changes these lines if you have a Dynamic Public IP
Use SSH keys and Strong passwords.
ufw allow from x.x.x.x/32 to any port 22 comment 'SSH for My Public IP'
ufw allow from x.x.x.x/32 to any port 51422 comment 'webmin for My Public IP'
to
ufw allow from any to any port 22 comment 'SSH for any'
ufw allow from any to any port 51422 comment 'webmin for any'

I try not running gaming servers as root of course. Ruby can be installed without Root. So lets create a user account to finish installing Ruby and run the web server on.

This will create a user account called inssserver

afterwards will ask for the password twice
create a strong password
Name section can be the same as inssserver
For the rest, click enter a few times to leave blank and confirm

You can start another SSH session and connect with the user account you just created
Installing Ruby with rbenv
***IF you don't have git installed run as root in other terminal window*** You probably have it already**

set up rbenv



Download the ruby-build plugin into the plugins folder of rbenv

Install Ruby
it may look like its idle for a bit, this is normal. Give it a few minutes.
When it finishes run this command

Verify Install
Should output something like this
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]

Install bundler with gem

Afterward run

Download a copy of sandstorm-admin-wrapper as a zip from
https://github.com/Joe-Klauza/sandstorm-admin-wrapper

Then Unzip and copy Contents to the SFTP window for the inssserver user. You should be in the Home folder if not sure then run command

I copy the contents to save a change directory command when reconnecting and starting the server.


To avoid a permission issue run

Make the start up script executable


Now lets do a trial run

if successful should see something like
2019-08-30 03:48:17 +0000 | INFO | Webserver initialized! Visit: https://127.0.0.1:51422

Press CTL + C to stop the server. We are not done yet :)
Since we do not have a browser on the VPS. We cannot connect 127.0.0.1. Lets change the config to Listen on all interfaces so we can connect to the public IP of the server.

In the SFTP window for the inssserver go to this path to edit config.toml
/home/inssserver/config/

I changed my Bitvise Client to use Visual Studio Code as the default text editor. We can just use notepad for the sake of the guide.

Right click config.toml and edit.

Find the line with
admin_interface_bind_ip = "127.0.0.1"
and change to
admin_interface_bind_ip = "0.0.0.0"

Save and close

restart the server in the inssserver terminal window with

Now we can use a browser on your computer.
Go To the public IP of server with the Sandstorm Admin Wrapper default Port
https://x.x.x.x:51422

NOTE: I suggest using the VPS provider Firewall to only allow your public IP to connect to TCP Port 51422 or Private IP if its on your LAN

You should see the Dashboard for Sandstorm Admin Wrapper log in with username: admin and password: password.

Download SteamCMD tar ball for Linux
https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz

Copy tar ball to
/home/inssserver/steamcmd/installation


change directory

Run Command to decompress tarball
You will have to stop the server. CTL+C if running

change permissions for steam install

make steam script executable

change directory

Start server

In the Dashboard should be able to click the install button under Server Setup. It will install Sandstorm.

Using the SAW SteamCMD tool change launch Param to

This is how I got it to work. If there is another way let me know.

for GSLT I used App ID 887860

To have the SAW server start up after reboot.

We are going to create a service and setup a Cron Job to start the service after reboot. As Root.
Stop the server if running.
There is an example in
/home/inssserver/extras/systemd/sandstorm-admin-wrapper.service

find and edit
sandstorm-admin-wrapper.service

I have already updated this example to work with this guide. Copy and paste replacing all text in file with below. save and close. You will have to update the User and WorkingDirectory VARs to work with your server, if not following this guide.

Then Copy the service to systemd and start the service by running this command as Root. .

Lets enable the service for Auto start up


-------------------------------------Start SAW and Sandstorm Server-----------------------------------------------
To start SAW and the Sandstorm Server after reboot. Once you have created a Sandstorm Server config.
Update sandstorm-admin-wrapper.service and Replace 'My Server' with your Server Name in the config.

Then Copy the service to systemd and start the service by running this command as Root. .

This would be good for if you want to manually start and stop SAW with out the Service Config. I am using Screen to run the SSH session and be able to close the terminal without fear of the Application closing.

When you are all finished installing and testing.
Stop the SAW with CTL + C
Type Command Screen to launch a Virtual screen

Then press Space Bar. It will launch the Screen.
Start Server.

After it is running.
Press CTL + A and D to Detach from Screen. Then it will be safe to close the Terminal Window.

To check/list for screens that are running.

It will list the current screens with output like
inssserver@inssserver:~$ screen -ls
There is a screen on:
28370.pts-1.inssserver2 (08/31/2019 03:15:28 AM) (Detached)
1 Socket in /run/screen/S-inssserver.

You can reattach with the PID/number like so
or

Kill a Screen session use CTL + A and K It will prompt y/n to confirm on the bottom of the terminal window.

Visit SAWs GitHub Page for more info like resetting password and other tips. Enjoy!

https://github.com/Joe-Klauza/sandstorm-admin-wrapper

Sandstorm Guide:
https://sandstorm-support.newworldinteractive.com/hc/en-us/articles/360049211072-Server-Admin-Guide

Requirements:
1. Steam GSLT

• https://psteamcommunity.yuanyoumao.com/dev/managegameservers
  
• Use this app id for the token: 581320
  

2. Must not have a password on the server
3. Cannot use with cheats enabled

In SAW config dashboard find the line with
Game Server Login Token (GSLT) [ ]
Add add token
save config and restart

If there is an issue with the steam query port
got around to testing it a symbolic link.

1. make sure the SAW server is not running and check to see if you have this folder sdk64 in this location /home/inssserver/steamcmd/.steam/
1a. if the sdk64 folder is not there create it

2. as Root run this to create symbolic link.


3. Start the server

4. watch the server console log output.
4a. make sure you DO NOT see these lines