This beta release includes a few fixes and improvements. It resolves an issue in the MariaDB build setup when SSL/TLS was enabled, fixes inaccuracies in packet loss calculation, and updates the S3 implementation to address occasional signature validation errors. Additionally, internal mutex handling and synchronization have been improved.
The default license has also been updated; the new expiration date is July 1st, 2026.
Fixed an issue in the MariaDB build setup when SSL/TLS was enabled
Fixed packet loss calculation inaccuracies
Updated the S3 implementation to resolve randomly occurring signature validation errors
Improved internal mutex handling and synchronization
Updated the default license
Please Note:
As always, feedback is welcome here. Please note that issues unrelated to this update should be discussed in their own dedicated threads.
We encourage you to share your suggestions for future releases in the appropriate threads within the suggestions and feedback area, rather than in the release thread. This is because update posts are typically closed after some time, and suggestions or feature requests may get overlooked.
We reserve the right to remove any off-topic posts from this thread.
Crazy idea, but maybe make the free license not expire every month? This is so unnecessarily hostile towards the people who are actively trying to adopt your product.
It’s not like people will start paying for your hosting after their server was broken the third time in a year, they’ll just stop using TeamSpeak.
I genuinely want you to succeed, but it seems like you really forgot the make a good product and gain a large userbase step before starting the enshittification process.
I’m not seeing how that has anything to do with the licensing. It would be trivial to either block connections from newer clients with an appropriate message or to just prevent the server from starting if it’s outdated. Having threads from people wondering why their server refuse to start once a month isn’t helping to reduce support workload, either.
The only reason I see to “solve” this via expiring licenses is if you plan to not include free licenses in future versions (or at least not with the same terms) and want to prevent people to continue using the beta servers license for free.
This is still a beta License not a free license
According to TeamSpeaks own release notes, it’s a “Default license”, not a beta license. Giving people not even two weeks to update the server before literally breaking it is simply not acceptable, even during a beta.
I don’t get why you’d defend this practice, it’s simply not in anyones interest to regularly break peoples servers.
So, for now, this is an unfinished version of TeamSpeak 6. When you start it up, you’ll also see a message telling you when the license expires. If you’re just looking for a version that works without needing updates, you can simply use the Teamspeak 3 server. (Even with this, you should update it if critical security vulnerabilities are found and fixed with a patch.)
Updating the server takes just a few seconds, and you already know that you’ll have to do this by the license expiration date at the latest.
The server has been in beta for about a year now, TeamSpeak 5/6 for over six years…
Updating the server takes just a few seconds, and you already know that you’ll have to do this by the license expiration date at the latest.
My issue is not updating the server, it’s that fact that TeamSpeak deliberately breaks server installations by including ridiculously short lived licenses.
There’s no word on licensing so far (at least to my knowledge), GitHub issues go without comments for months. The silence from TeamSpeak staff about this is deafeningly loud any anything but confidence-inspiring.
The fact that they only upgraded the default license from 5(!) to 32 slots after a bunch of criticism is also supporting my point about them being hostile towards self-hosters.
v6.0.0-beta10 Changelog 
What’s New
This is still a beta License not a free license