I managed to login via putty and selected the correct virtualserver,
then used clientlist to get my cldbid which is 4.
Finally i tried to add myself to the servergroup query admin and it gave me this: login serveradmin "pw" error id=0 msg=ok use 1 error id=0 msg=ok clientlist clid=5 cid=1 client_database_id=1 client_nickname=serveradmin client_type=1|clid=3 cid=1 client_database_id=4 client_nickname=ADMIN client_type=0 error id=0 msg=ok servergroupaddclient sgid=2 cldbid=4 error id=512 msg=invalid\sclientID
My question:
What was my mistake and how to fix that to become query admin?
Hello I have a problem I want to put myself on the server in the Admin Server Query group which is not possible because I always get an error
error code 512
invalid clientID
This feature was removed in the server version 3.6.0 - so a long time ago.
You can’t get it into an official way anymore.
The only thing you can do is, logging in as serveradmin
Sooo this query should include the Admin Server Query group automatically… and you’ll be able to use it, but of course not as a client; just as a server query.
As a quick tip: If you just want to manage the server you can mostly use query tools like YaTQa. They are fairly easy to use and give you all the possibilities you had on older server versions with the query group as a client.
Yes. Usually 75 is more than enough. You could just decrease everything else.
If you really want to use the system up to 100 you have to manage the settings via the query.
Either plain Telnet or a query client.
I really need some help! Does anyone know how to create an additional separate ServerQuery user with admin rights?
I mean the same type of account that TeamSpeak itself creates when the server is first set up, like this:
Server Query Admin Account created loginname= “serveradmin”, password= “hidden” apikey= “BACEnvPKlYd…”
When I create a user through the TeamSpeak interface, it only makes a regular user that inherits my server groups. But what I need is a completely new separate serveradmin account with a different ID in the server logs.
The reason is that I want to run multiple bots, and if they all use the same Server Query Account, their messages overlap in the logs. With separate accounts, each bot would be properly logged under its own ID.
The Server Query will operate under the identity used to create the login. This means you’ll need to assign the required permissions to the server group that is assigned to that identity.
We do not recommend and no longer allow users to acquire Server Admin Query group, as this may lead to misconfigured servers that cannot be recovered.
If you still require those permissions, you can duplicate the group into a new Server Group (not a Query Group).
Please note that we do not endorse this approach and you should proceed with caution.