it works for you because you probably started the server and started it on P2P instead of the server connection which is still not on the servers hosted with us.
It was not mentioned in the post that the function already exists in the version. This will probably follow in later updates
Anyone else problems with creating permanent channels with latest TS6 client? On TS3 I can create permanent channels, on TS6 only temporary.
have you used the token to authentificate? you need permission to create a permanent channel.
yes, I did
It works on Linux wdym?
Ok, i fired up a docker container and managed to log in with the v6 client. But how do i get a privilege key?
check container logs
1 Like
no key in there what would it say?
are u sure? it should like this, in the important “tab”, the token. are u really looking in the first log created?
Server logs
2025-07-01 17:22:57.636748|INFO |ServerLibPriv | |TeamSpeak Server v6.0.0-beta2 (2025-07-01 12:06:57)
2025-07-01 17:22:57.636878|INFO |ServerLibPriv | |SystemInformation: Linux 6.8.12-11-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-11 (2025-05-22T09:39Z) x86_64 Binary: 64bit
2025-07-01 17:22:57.637091|INFO | | |checking database integrity (may take a while)
2025-07-01 17:22:57.642284|WARNING |Accounting | |Unable to open /var/tsserver/licensekey.dat
2025-07-01 17:22:57.642441|INFO |Accounting | |Licensing Information
2025-07-01 17:22:57.642487|INFO |Accounting | |licensed to : TeamSpeak Systems GmbH
2025-07-01 17:22:57.642506|INFO |Accounting | |type : No License
2025-07-01 17:22:57.642526|INFO |Accounting | |starting date : Tue Apr 1 00:00:00 2025
2025-07-01 17:22:57.642542|INFO |Accounting | |ending date : Mon Jan 19 00:00:00 2026
2025-07-01 17:22:57.642564|INFO |Accounting | |max virtualservers: 1
2025-07-01 17:22:57.642584|INFO |Accounting | |max slots : 5
2025-07-01 17:22:57.693873|INFO | | |Precomputing puzzle, this may take some seconds...
2025-07-01 17:22:58.434709|INFO | | |Puzzle precompute time: 740
2025-07-01 17:22:58.434945|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2025-07-01 17:22:58.435345|INFO |Query | |Using a query thread pool size of 2
2025-07-01 17:22:58.438436|INFO |VirtualServerBase|1 |listening on 0.0.0.0:9987, [::]:9987
2025-07-01 17:22:58.438654|INFO |CIDRManager | |updated query_ip_allowlist ips: 127.0.0.1/32, ::1/128,
2025-07-01 17:22:58.849458|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
thats all i have in my logs 
Please have a look at the other logs. There is a different log in which the privilege key gets written when using the binaries.
3 Likes
i used the docker compose text from the docker page and pasted it into portainer as a new stack.
it fired up the container just fine. i logged in just fine locally. What other logs are there? i ssh’d into my docker machine and typed "sudo docker logs <container id#> and that was all the text it returned, im probably missing something but im really new to docker/portainer
the admin key is only on the first startup of the container in the logs. they get overwritten every restart. So just stop the container remove the persistent data and start the container again and check the logs
1 Like
Soooo i deployed the server inside kubernetes and it works (almost)flawless, using mariadb as database server also no issues.
I’ve tested the streaming in a few scenarios.
Me > Laptop on same network → Perfekt
Me > Laptop on moblie hotspot → Perfekt
Now comes the strange part.
Me > A friend ~300km away → Bandwith limit error with lots of retransmissions
But
Same friend > Me → Perfekt
We also tried around with hoping into the same vpn network and even him tunneling over vpn into my local network, but no matter what he can’t receive my stream without a lot of Re-Transmissions and the Upstream not going over 1Mbps.
Before someone says it’s my upload, it worked fine when i streamed to my Laptop when connected over LTE
(The spike is the start of the stream, but after that it stays like this when i’m streaming to him)
The container just crashes after this message and can’t start at all, I’ve seen multiple messages like that so decided to also report my case. I’ve tried running container in RouterOS, and got the same message
This is 1vCPU 1GB RouterOS server (x86 CHR) so maybe low resource is an issue. Starts fine on Ubuntu 24 LTS. As you may see on screenshot, assert message comes, then container crashes with code 1. I’ve started it manually again and the behavior is the same. As you may see above, this is first start of the container.
got it. thanks all 
you rock!
use “–threads-voice-udp 1” as starting command, then it should be working.
2 Likes
