TS6 Server BETA - v6.0.0-beta9

Announcements
, ,
1

Hey everyone! :waving_hand:

This beta release introduces native ARM64 support and includes several important improvements and fixes. It enhances server migration notifications for clients, resolves a crash that could occur when flushing with invalid database connections, and significantly improves S3 performance through optimization.

The default license has also been updated; the new expiration date is June 1st, 2026.

You can get the latest server release here:
– GitHub: Release v6.0.0-beta9 · teamspeak/teamspeak6-server
– Docker Hub: Release v6.0.0-beta9 · teamspeaksystems/teamspeak6-server

Forum Splitter
Forum Splitter1500×150 11 KB

:memo: v6.0.0-beta9 Changelog :memo:

:sparkles: What’s New

  • Added native ARM64 support
  • Improved server migration notifications for clients
  • Resolved a crash that occurred when flushing with invalid database connections
  • Optimized S3 implementation to significantly enhance performance
  • 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.
Don't miss any future Announcements
22 Likes
3

So nothing that actually improves user experience?

1 Like
4

I mean it improves the server stability, so for now the update was worth it…

5

Very underwhelming

1 Like
6

People have been asking for native ARM64 support since around 2017 and it’s finally here, I wouldn’t call that underwhelming.

12 Likes
7

Yeah, it has been asked a lot, i have even used ARM before for a long time via box64 emulation, but it took so much time to release ARM native version that i left ARM behind. Other than ARM support there isn’t anything interesting, which is sad when we waited 3 months for only this from the release before.

8

When is this update deployed to the community-server variants?

Thank you for your work!

9

I was really hoping this update would include server-side streaming…
Is the feature being developed? Any ETA for it?

3 Likes
10

I have a TS6 server running in docker-compose, using theTZ=Europe/Madrid environment variable. I’ve noticed that the container time (command date) and the server chat time are both correct, but the container logs are still 2 hours behind my local time.

It’s nothing critical, but unless I’m missing something, it seems the logs are always using UTC+0.

11

Perhaps you are missing the docker host timezone?

Commands that might help (execute them on the host, not the container):

date

timedatectl

timedatectl set-timezone

12

Man, updates are so easy now with docker, two command and done, as long as it goes smoothly.

8 Likes
13

Get the watchtower container and it will autoscan for docker container updates and auto update for you.

15

Any update on allow Screensharing via the server instead of P2P?

1 Like
16

Heads up for anyone updating from beta8: the Docker image now runs as user teamspeak (previously tsserver), UID/GID 9987 unchanged. This change is not mentioned in the changelog.

If your container fails to start with:

Error response from daemon: unable to find user tsserver: no matching entries in passwd file

…the fix is to remove the old container and recreate it:

docker rm -f <container_name>
docker compose up -d

If you use a bind mount instead of a named volume, also run:

chown -R 9987:9987 ./teamspeak-data/
3 Likes
17

Thanks for the heads-up about UID/GID change for Docker install folks!!

I’d like to add, for those who are new to self-hosting and NOT using a containerized approach such as Docker, you will need to update TS using the same userid as before.

Also, I would like to recommend the TS team update and extend the default beta license to allow a longer grace period in-between server version updates. Meaning, when beta10 comes out, that the beta9 license is updated so that we admins have ample time to react and update.

I happened to be out on holiday when the beta8 license expired, and while my server is just myself and a handful of friends, it was a bit irritating to hear about server outage. They are very happy that the box is back online AND with more features than before (markup is HUGE for us, merci beaucoup!!!)

1 Like
18

Its just sad, but what can we do ;-;