Setup Guide
Everything you'll need to know to create your own self-hosted server.
Creating a Server Config
Before we can get your server set up, you'll first have to decide how you're planning to use it. You'll choose a domain name, configure privacy settings, and select the software you want to host. Your choices of software and settings are stored as part of your server configuration or "Config" for short. This config allows your server to know what software to deploy for you and how to configure it automatically. (Step 3)
Click here to create a new server config under your account
1: Choose a domain name for your server
The first step is to define how people will access your server. You have a few options here. If you want your server publicly accessible over the internet, for example to host a website, you can either choose a free DDNS domain or provide your own if you already have one. Providing your own allows you to have a domain with a nice extension such as "example.com", which is preferable for things like websites.
In contrast, a DDNS domain will always have ".ddns.net" at the end, like "example.ddns.net". This is a good choice for things like game servers, where all you need is a persistent address to paste into a game client once. Note that if you choose to use your own domain you will have to define a static IP address for your server in your router's settings and configure the associated nameservers manually. If you don't know what this means, you should probably choose DDNS as it requires no further setup.
If you're only planning on hosting your server privately on your own local area network (LAN), you can opt to forego a domain name entirely. You can also choose a DDNS domain specifically for this purpose, for example "manage.myserver.ddns.net" if you'd prefer.
Read more about domains and DDNS
2: Configure remote access
Next, you can choose if and how you want support staff to be able to help you manage your server. If you want to be able to manage your server remotely yourself or you would like us to be able to do it for you, leave Secure Shell (SSH) enabled. SSH is a protocol that allows those with authorization to connect remotely to your server for management purposes. For a completely locked down system you can turn SSH off, but note that we will be unable to remotely assist you unless you enable it later.
By default, even with SSH enabled we still can't access your server. You must first explicitly grant us access. You can either do this manually once your server is set up, or you can enable Quick Support to grant us access as soon as your server is deployed.
Read more about remote support
3: Configure metrics
Next, you can choose what status metrics you'd like to keep track of. This includes things such as remaining storage capacity, processor temperature, network speeds, etc. This allows us to get a better picture of the health of your server, and can be extremely helpful in narrowing down and resolving potential issues. It's recommended you leave all metrics on, unless you have a specific reason you'd like to disable them. The metrics we collect are non-sensitive, consisting only of things like system speeds, utilization as percentages, and hardware temperatures. We do not collect any information regarding the actual usage of your server beyond these very broad performance statistics. All the data we collect is made fully available to you, and you can choose to permanently delete it at any time.
4: Choose a port forwarding method
In order for your server to be reachable over the public internet, you will have to forward any ports required by your software. This means telling your router to allow traffic to/from the external internet through to your server. There are two ways of doing this, one being more secure and one requiring less work to set up:
-
Manual: You will have to go into your router's configuration page and add a new "rule" for each required port. A list of all required ports is provided once you've finished creating your config. This exact process varies depending on your specific router. Click here for a guide on how to do this: GUIDE: Manual Port Forwarding
-
Automatic: You will have to ensure your router supports Universal Plug and Play (UPnP) and that it is enabled. Your server will handle the rest. Click here for a guide on how to do this: GUIDE: Enabling UPnP
5: Selecting your software
The next step is the most important: Actually choosing the software you want to run. Are you planning on hosting your own personal Wordpress site? A cloud storage solution for your office? Maybe a game server to play with friends? See our comprehensive Software Catalog to see what we currently support for automatic deployment. If there's a specific software package you'd like to host that isn't currently supported, please open an inquiry Support Ticket and we'll look into adding support for it. You can also install your own software manually using the terminal once your server is up and running if this is something you're comfortable doing.
Note that most software has additional settings specific to it that you can tweak if you wish. When you click on an entry in the software selection panel, a software-specific configuration form will be shown if applicable. Some settings are required, others are optional or marked as advanced. In general, you should only change advanced settings if you have a specific reason and know what you're doing. Brief descriptions of each setting are provided, and more detailed information can be found through the Software Catalog.
Some examples of software settings might be locations where data is to be stored, a whitelist of allowed users, what ports the software communicates through, etc.
Next Step: OS Installation
Now that you've created your config, it's time to actually install TableOS onto your computer. This will convert it into a server capable of deploying and hosting your chosen software. This will involve booting from an Easy-Install USB and clicking continue a few times.