Hi!
To start the server, first you have to set the permissions to the server file. To do that type

chmod +x ./tt5srv
It will set the permission for tt5srv file. Then, type
./tt5srv
This command will launch the file tt5srv.

Ok, here's the scoop on Vultr. To create the server, you're gonna want to use a lot of virtual focus and clicking, nvda object navigation works best for this. Go to Vultr and click on deploy instance. What you'll be presented with is first a list of country, I was presented with 5, and then a list of cities for close proximity. Where you click depends on what you want. For example, since Chicago Illinois was a location below the list of 5 countries, I clicked on that. Keep in mind that while the cities are one per line, the list of 5 or so countries will appear as a block of text. So for this, what you wanna do here is move by character to the first character of the country you want, then hit insert+shift+m to move the mouse cursor to that element. Then hit insert+left bracket to do a left click on that item. You'll want to remember these two commands as you'll be using them throughout this whole process. As for the cities, you'll do the same insert+shift+m to focus, left click to activate however it will be easier as all the cities are separated by a line. Still, it's safe to hit the home key on a line just to make sure it's focused, insert+shift+m to focus, left click to activate. The next heading is the server type, move your cursor to the 6 on 64bit operating system, focus, then click on that. Next, os selection. There will be a line that says, debian select version. Focus and click on that. Then there will be some new clickable elements, you want to focus and click on 7x64 for debian 7x64. Next there will be the hd space, memory and cpu selection. A decent one for your purposes is the 20gb ssd so focus on the 20gb ssd line, focus and click on that. After extra features, there are two more settings you wanna configure, and that's host name, you could type sljVultr for example, this is what you'll be connecting to via ssh. The label edit box allows you to label it you can type the same thing, click deploy and you're good to go! It'll show that it's now installing debian7 onto your server. The installing status isn't in realtime, so I'd say wait 5 or so minutes for the operating system to install, then refresh your browser. Now you should click on, for once, an actual clickable link! that should be labeled as whatever you named your vultr server. It will give you the overview, in which there are 3 things you should look for. Your ip address, the username *should be root* and your password. The password i hidden by default, click the show password link, or the copy password link to automatically copy it. Now, you can use terminal on the mac, or whatever you use to access ssh, and do ssh [email protected] replacing those characters with your actual ip of course, then hit enter. You'll get a warning about adding the ssh key into /users/username/.ssh/known_hosts, but since this is your own server this shouldn't be a problem, just type yes and hit enter. Now type or paste in your password. You'll know it's successful when you start to hear the standard debian disclaimer, and get placed in the root of your server. The rest is accessible from here on out.

No problem. Supposedly Vultr has a special promotion going right now if you make a $10 balance reload, and they give free credit as well if you follow @vultr on twitter. Many opportunities to gain more free credit. And there's always Vultr's hourly rates so if you wanted to do a bigger project but not a constant one, like an temporary internet radio stream without automation, then Vultr's hourly would be the right choice. Nevertheless, if you want to switch between the two for your different needs that is also very doable, because as long as you're using the same linux installation on both servers, operation of them is exactly the same.

A quick question which I can't find much information about on the internet:
I accidentally started the Teamtalk server as none daemon. This means I  can't enter commands in the terminal. Is there any way to switch between the open application and the terminal or go back to the terminal without rebooting the server from the dashboard?

You certainly jumped in at the deep end, didn't you? This is why I generally prefer to explain Linux from the bottom to the top, rather than the other way around--there's a lot of fundamental stuff you should really know before you go playing with fire, and getting confused and frustrated. Nevertheless, congratulations on having got where you are.

And to answer some of your questions: the way to get ls to print in a single column is to use the -1 switch, to identify types using either the -l (long) or -F (types) switches, and to show all files (including files starting with a dot) using the -a switch. Then tar is usually started with either c for create and x for extract, z for gzip compression or j for bzip2 compression, and f filename for a file instead of standard input. What's standard input? You need to do some homework to answer that question, but by way of example, try typing "ls -la /Bin|more". Oh, and daemons can't be controlled once they have gone into the background; if you'd wanted to do that, you'd already have the means to communicate with the daemon by some other methods. Learn about job control in your shell if you'd like to learn about switching tasks, start multiple shells by connecting again using ssh, and kill processes using the kill and killall commands. Check the manual pages for this stuff for full details, as well as that of your shell, bash (warning: very, very long page!).

This looks like a promising tutorial.

I don't have easy access to chat stuff. Email and this forum work well though. If you find I'm slow to answer, feel free to just mail me. I'm sure we can sort you out if you get really badly confused.

@SLJ no problem; feel free to mail me if you need (it's right there on all my posts).

By learning from the bottom up, I mean you should start with the mechanics and principles and go upward, instead of trying to digest everything necessary, at once, in order to achieve some complex task that's on your mind from the outset. UNIX is not user-friendly--or at least, it's picky about who its friends are. You have to learn the building blocks, so you can create your own solutions. Once you understand the simplicity of the UNIX philosophy, and how each individual piece of the puzzle is best suited to a particular problem in its own right, and how to combine those blocks together, you will begin to appreciate just how powerful the tools you have are.

So in summary: carry on learning.