"Is this your TeamSpeak server?" message does not disappear, even after using the key

TeamSpeak 6 Server
,
1

Hello all,

I have a minor issue, everyone that is not admin and connects gets the “Is this your TeamSpeak server?” prompt for the privilege key.

I deleted all privilege keys, message still there.
I created a new one and used it, message still there.

I eventually found out that “virtualserver_ask_for_privilegekey” is set to 1. I cannot edit it via serveredit and I cannot even find it in the server_properties of the tsserver.sqlitedb (creating it in there and setting it as 0 also had no effect).

How do I now get rid of the message?

2

Have you use the privilege key that was printed in the logs or have you assigned yourself permissions directly via the ServerQuery?

2 Likes
3

I used the query.

4

I can not confirm this issue.

Steps I did:

  • Create a new server
  • Used the Query to grant myself Server Admin group
  • Deleted the default privilege key

Once the key was deleted the “Is this your TeamSpeak Server?” disappeared.

What is the output when you type in this Query command?

privilegekeylist
3 Likes
5

serveradmin@9987(1):online> privilegekeylist
error id=1281 msg=database\sempty\sresult\sset

Just reconfirmed, the message is still there.

image
image595×203 30.4 KB

6

Can you guide my trough your steps you’ve done to result in this specific scenario?

Have you manually modified the database with a a DB viewer?

Does the message disappear when creating a server snapshot and deploying it again?

2 Likes
7

Sorry if I’m being an idiot here but I cannot for the life of me deploy the snapshot.

If I run “serversnapshotcreate” the result is so long I cannot paste it back to run “serversnapshotdeploy”, it always gets cut off. I tried regenerating the snapshot multiple times.
I tried YaTQA, Putty and just running ssh in a Terminal (both Windows and Linux).

The reply to “serversnapshotcreate” is 10416 characters long. Is this normal?

8

You haven’t answered my previous questions:

Can you guide my trough your steps you’ve done to result in this specific scenario?

Have you manually modified the database with a a DB viewer?

Pasting a big server snapshot exceeded the SSH limit. As workaround you can write the snapshot data into a file and then use that for the deployment.

Powershell Example

Serversnapshotcreate

"use 1", "serversnapshotcreate", "quit" | ssh -tt serveradmin@localhost -p 10022 | Select-String '^version=3 data=' | ForEach-Object { $_.Line } | Out-File -Encoding ascii -NoNewline snapshot

Serversnapshotdeploy

("use 1`nserversnapshotdeploy " + (Get-Content -Raw -Encoding ascii snapshot)) | ssh serveradmin@localhost -p 10022

bash Example

Serversnapshotcreate

( echo -e "use 1\nserversnapshotcreate\nquit" ) | ssh -tt serveradmin@localhost -p 10022 | grep '^version=3 data=' > snapshot

Serversnapshotdeploy

( echo -n "use 1\nserversnapshotdeploy "; cat snapshot ) | ssh serveradmin@localhost -p 10022
2 Likes
9

I cannot tell you how exactly I got here, I cannot recall doing anything special in particular.

Anyway, thanks for those commands - that worked and the server is no longer asking for the key after deploying the snapshot.

1 Like