Newbie Questions

[InvisibleMan]

I installed TS successfully on my linux box. I tested it, works fine via admin/superadmin web interface and connection works fine on UDP port(s) specified.

Questions:

I started the TS server via root and installed TS via shell in root mode. Is this ok?

Created TS server and applied an admin via SA web interface. Started server. Is it safe to forward login / UDP port infor for the client's TS server considering the above (starting TS in root / installed in root)?

Thank you.

[InvisibleMan]

Any help appreciated. Thank you

[mrdeath]

Install with root is ok.. but its recommended to run as a normal user (i.e. "teamspeak").. I'm sure there is post about how to do this properly .. fairly many guides around..

[InvisibleMan]

Thank you for your reply.

Is there any way to know the Query port, so I may list the people on the Server on a block on my clients website? I gave her port 8700 (she is not using a full dedicated server either).

Her reply:

"I am using an add-on for my site that asks for the server's Query Port so that it can display the people currently talking on the server. It says that the information is in the server.ini file, which I obviously don't have access to (for good reason, I'm sure I'd mess something up!)."

Thank you

[mrdeath]

I'm not sure what you are asking here.. but query port (TCPQueryPort) can be found in the server.ini file;
[Main Config]
ExternalIPDectection=1
HTTPServer Port=9999
HTTPServer Enabled=1
DateTimeFormat=dd-mm-yyyy hh:nn:ss
TCPQueryPort=51234
BoundToIp1=
AllowedClientNameChars=
DisAllowedClientNameChars=()[]{}

[InvisibleMan]

Right but is it safe to give that port to customers who do not have root access to the server?

[mrdeath]

Think your mixing stuff here. It’s only the TeamSpeak app. that answers on that port, you don't gain access to the operating system directly (even if it access files, its files that’s been programmed by the TeamSpeak team, not a script on a web site (or whatever)).

And if you run TeamSpeak with other user then “root” there is even less of a chance that “things go wrong”. As I see it the only thing that can be done is messing up the TeamSpeak server (settings/users etc.) and that’s by guessing a password or something like that. But with a backup plan that not really a problem and the use of complex passwords (and of course setting up rights in a thoughtful way)…