TS6 Server BETA | Addressing Your Feedback

Hey everyone,

We’ve received a lot of feedback, criticism, and have seen a lot of frustration regarding the TeamSpeak 6 Server Beta Testing.

In response, we made a quick decision based on your feedback. Starting now, the latest TS6 Server beta release, v6.0.0-beta4, will include a 32-Slot License valid for two months, which will expire on Monday, September 1st. We hope this gives you more flexibility during the initial testing phase.

Link to v6.0.0-beta4: Release v6.0.0-beta4 · teamspeak/teamspeak6-server

To clarify our intent, this is a beta release, which means the server is still a work in progress and not intended for production use. We will be updating the server and license more frequently during this phase, so you are not stuck on outdated builds or restricted by old license limitations.

We truly appreciate everyone who took the time to share feedback. Your enthusiasm and input are incredibly valuable. We did not mean to disappoint or frustrate anyone with the initial slot limit. The original 5-Slot Setup was intended for controlled testing, but we now understand that it was too limited for many use cases. We’ve heard from many of you that your friend groups are larger than five people, and being forced to exclude friends or set up multiple servers to participate in the beta is far from ideal. That’s not the kind of experience we want anyone to have, especially during a beta that’s meant to be collaborative and community-driven. This 32-Slot License is a temporary solution that will help us better evaluate how to move forward with the beta.

Please keep in mind that this version is still in beta. It does not represent the final product in terms of features, performance, or limitations.

Thank you again for your continued support and feedback.

36 Likes

This is good news. Thank you very much for responding so quickly and flexibly to the justified criticism and temporarily increasing the slots!

6 Likes

Thank you for the update!

Is there a recommended update procedure for those not using docker?

I stopped the server, copied over the files from beta4 → replace any files as needed. Started the server.

The server kept the channels, and shows v6.0.0-beta4, but the user count is 1/5. On a fresh beta4, it shows 1/32. I can’t remember what the normal update procedure was for TeamSpeak 3. Any help would be appreciated.

That is the way to do it, you now need to change the slot count in the server settings.

Your database was already generated once, therefore the slots will stay the same when upgrading to the new version.

5 Likes

Thank you, that worked!

Can you please provide more transparency about licensing costs for self-hosted servers in the future?

5 Likes

I have a bad feeling about this… especially considering the fact that they’re providing a license here, instead of just increasing the slots to 32 in the default unlicensed version.
You might as well prepare yourselves for the fact that the free, self-hosted server will only offer 5 slots.

Oh well… be that as it may. Thanks anyway for listening to the feedback.

5 Likes

Only two ports are open: 9987 and 30033. What about the ServerQuery port (10011/10022)?

1 Like

Now we’re talking. Time to get people to move over to TeamSpeak.

not now XD

Yeah, at first I tried copying all the channels using WinSCP/FileZilla so I’d have the permissions and channels from the old server, but that didn’t work. Then I tried with YatQA, but it won’t let me connect… I hope there’s still a way to get access copying the entire server otherwise would be a bit annoying.

So, with TS3 server I used the teamspeak3_startscript.sh, I’ve attempted to just do a quick update to point so the new binary, but it didn’t like the pid_file parameter. Is there a recommended script setup for the new server. Would rather not have to run it in screen every time I start the server.

You can try running the TS6 server in daemon mode, use a systemd service (optionally managing the PID file), use Supervisor as a process manager, or run it using a Docker image

  1. Daemon mode
./tsserver --accept-license --daemon
  1. Systemd service
  • Create systemd service file:
sudo vim /etc/systemd/system/tsserver.service
[Unit]
Description=TeamSpeak 6 Server
After=network.target

[Service]
Type=forking
User=ts
WorkingDirectory=/home/ts/teamspeak-server_linux_amd64
ExecStartPre=/bin/rm -f /home/ts/teamspeak-server_linux_amd64/tsserver.pid
ExecStart=/home/ts/teamspeak-server_linux_amd64/tsserver --accept-license --daemon --pid-file tsserver.pid
PIDFile=/home/ts/teamspeak-server_linux_amd64/tsserver.pid
ExecStop=/bin/kill -TERM $MAINPID
TimeoutStopSec=30
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
  • Reload daemon:
sudo systemctl daemon-reload
  • Start service:
sudo systemctl start tsserver
  • You can enable the service to start automatically on boot:
sudo systemctl enable tsserver
  1. Process manager (Supervisor)
  • Install Supervisor:
sudo apt install supervisor
  • Enable and start the Supervisor service:
sudo systemctl enable supervisor
sudo systemctl start supervisor
  • Create Supervisor program file:
sudo vim /etc/supervisor/conf.d/tsserver.conf
[program:tsserver]
command=/home/ts/teamspeak-server_linux_amd64/tsserver --accept-license
user=ts
autostart=true
autorestart=true
directory=/home/ts/teamspeak-server_linux_amd64
stopwaitsecs=30
  • Reload Supervisor:
sudo supervisorctl reload
  1. Docker image
    See official docs - teamspeak/teamspeak6-server: This TeamSpeak 6 Server Beta repository contains the latest beta version of the TeamSpeak 6 Server software, offering early access to improvements and bug fixes. This beta release is intended for testing and feedback before the stable version launch.
2 Likes

2025-08-31T21:00:00Z I hope ServerQuery comes back

1 Like

Same here, they’re making a point about the 32-slot license expiring in two months. How do they expect us to take that? Let’s hope it’s not the case but if it is, I’m sure it will kill basically all good will TeamSpeak currently has with its users and no Twitter memer is going to be able to spin that into a good thing.

Was hoping for competition to Discord, would be a big shame!

2 Likes

Oh, you can be pretty sure that’s how it’s going to go. Now they’ll want to squeeze more money out of the community too. Apparently, their wallet isn’t big enough yet.
In any case, I’m done with Teamspeak. You just can’t trust that team.

1 Like

Thanks for adjusting so fast to 32 slots <3
Will there be 32 slots for free when self hosting?

1 Like

Interested to know what server pricing would be. I understand needing to have some licensing fee.

I would expect it to be cheaper than purchasing a community as well seeing as the server resources are not something we would need.

I speculate around $100 USD for an annual license, they may offer a perpetual license that we can use for a couple years until TeamSpeak 7, etc. The annual price for a community with 25 slots is $97, so I would think that price would fit for a selfhosted 32-slot server.

Everyone has their own opinions, but for me, someone who has hosted TeamSpeak for 12 years, and haven’t given a dime, I have no issue with this. If you consider the fact that one of your friends is likely paying for Discord Nitro so we can screen share, we are actually saving money.

My guess is TeamSpeak just doesn’t know what the pricing model will be. Sure, a 32-slot selfhosted TS3 server is free… but there hasn’t been a server update in how long now. So I’m hoping extra income will help TeamSpeak expand.

1 Like

I have an active ts3 gamer license. Will it be possible to port the license to ts6?