[Tutorial] Installing a TeamSpeak server on Linux.

[Recursion]

Hey,

I thought that after installing a couple of teamservers for someone and wanting to get back onto the whole webdesign scene again that I would start off with a simple tutorial :).

For this I will be connecting to a VPS of mine (running CentOS) through SSH using PuTTY (http://chiark.greenend.org.uk/%7Esgtatham/putty/).

You'll want to start by downloading PuTTY from the link above and connecting to your VPS/Server as root.

First of all, you'll want to create a new user for your TeamSpeak server to run from, for security's sake, so what we'll do is create a user called "teamserver" with the home directory of "/home/teamserver":


useradd -d /home/teamserver teamserver
Now, switch to the "teamserver" user and change directory into "teamserver"'s home directory that you set, remember?


su teamserver
cd /home/teamserver
Now we're going to download the core TeamSpeak server files from the TeamSpeak website, you do this with the WGET command, when you do this it will save the .tar.bz2 file into the TeamSpeak home directory:


wget ftp://ftp.freenet.de/pub/4players/teamspeak.org/releases/ts2_server_rc2_20201.tar.bz2
And you'll want to untar them into it's own folder with:


tar -xjf ts2_server_rc2_20201.tar.bz2
Tip! You can just type in "ts2" and then press tab, Linux will then automatically fill in the file name for you!

That's pretty much it for installation, now you'll want to run the server. Remember that change directory command? Then start the server once you're inside the directory, remember, just type "./team" or something, press tab and Linux will fill the file name in so you just finish it off with start:


cd tss2_rc2
./teamspeak2-server_startscript start
Okay, so you can now connect to your TeamSpeak server et all, but you want to get at the Administrator's panel at http://URL:14534 only to find it asks for a password! Oh no! :( But this is easy. When you first ran your server, it created an Admin and SuperAdmin password. To view these just use the following while still in the server directory:


nano server.log
Look for these lines:
http://www.*****.co.uk/teamspeaktut.png

Here you can see it has created "admin" and "superadmin" users, where the yellow blobs are will be your passwords for the TeamSpeak administration panel.

To exit the NANO text editor use CTRL X and press N so that you don't save, you should now have a fully functioning TeamSpeak2 server! :)

If there's anything I have missed or I could do to make this better than please let me know! :)

[Mentor]

For most, wouldn't the equivalent, depending on your package manager, of

sudo apt-get install teamspeak

do the trick? at least for the basic installation

[Recursion]

This one is how a MAN does it j/k. Well, it can be used for any distrobution, whereas something like apt-get is distrobution-based and I'm not sure if TeamSpeak is in the RPM repositories or not. Also, for a newbie apt-getting the teamspeak install will just be more complicated, they won't know where it was installed to or how to run it under a specific user.

[Source]

Your right, men do it from a download and not apt :P Nice tutorial for those new to linux out there, however there are thousands on the internet.

[Recursion]

True dat, but generally they don't stop and think to Google it. ;)

[Source]

Maybe a small linux resource site would be handy? Like a wiki for everything linux, and how todo basic things in a user friendly way. Maybe we should do something Android man.

[Recursion]

Maybe we should, Dave Taylor started one a couple of yrs back... wonder what happened to it.

A wiki site based on contributions would be good :P

[eight]

thanks for this

[Mentor]

This one is how a MAN does it j/k. Well, it can be used for any distrobution, whereas something like apt-get is distrobution-based and I'm not sure if TeamSpeak is in the RPM repositories or not. Also, for a newbie apt-getting the teamspeak install will just be more complicated, they won't know where it was installed to or how to run it under a specific user.

Its in the repos, and real men are lazy :P I use linux because it can get things done faster, not to slow myself down. Also shouldn't "real men" be building from source... that or writing there own out of love or reinventing the wheel, of cause it would then have to run on the O/S they made, that runs on the hardware they built :p (I actually have a lecturer who has done this, bar the teamspeak server part >.<)

Point is, you can make any task as difficult as you like, personally id rather run a tiny command and have it all done for me, just because you can do something, dont mean you should.

Just my two cents :)

[Source]

You seem to miss the point of this thread. The point is to help people learn how to do it the more complex way, for example if you don't use a distro that has apt-get or yum. There is no point using apt-get, if you don't have the knowledge to fix something when it goes wrong. This of course applies to all packages, not just teamspeak.

I use apt quite a lot, as I don't want to mess around compiling source or setting things up. But I think its important to have the knowledge.

[Mentor]

You seem to miss the point of this thread. The point is to help people learn how to do it the more complex way, for example if you don't use a distro that has apt-get or yum. There is no point using apt-get, if you don't have the knowledge to fix something when it goes wrong. This of course applies to all packages, not just teamspeak.

I use apt quite a lot, as I don't want to mess around compiling source or setting things up. But I think its important to have the knowledge.

Its not really doing anything the hard way, just the long way. Uncompressing some files and creating a directory are pretty basic skills. As is creating a user account, sure command line is a better way to set this up but its still not what i would conciser advanced.
If anything it just leaves more room for problems, especially considering your pretty much ignoring any dependency that may occur (handled by apt in debain/ubuntu + others etc) without really helping to solve any.

almost all distros will come with some form of package manager/dependency resolution tool, so seems weird not to use em.