TeamSpeak 6 Server - BETA RELEASE v6.0.0-beta2

Great work. Working very well!

Waiting for everything to stabilize and then I’ll transfer my TS3 server to TS6. Both in Docker working together (except File Transfer because the port is already being used).

I currently use ZimaOS, but plan to migrate to Proxmox soon. I just need to test the Web Query system to be able to backup like TS3.

FLP

The server is working well so far. (Ubuntu 24.04)
The client completely froze when watching the stream once, after rebooting it has not happened again. There is no way to estimate what it was yet.

Sound streaming on Ubuntu 24.04 with KDE is problematic. The toggle switch is not active. Streaming the entire screen does not transmit sound from Firefox.

yes but to use them is not good

it need a GUI not only the “hotlink” thing

1 Like

Ubuntu 24.04 with KDE Plasma.
When watching a stream, volume control does not work. The sound is always at maximum volume.
Muting the stream does not work either.

After restarting the viewing, the slider returned to normal.

1 Like

Appreciate all of the work that went into the Teamspeak 6 server beta release and it’s working well from my setup (on Ubuntu Server 24.04) with limited testing, but adding to the requests for more than 5 slots. I was planning to switch our small community over to this beta immediately and try to provide some good feedback/testing but 5 slots is too tight a limit even for a very small community, please consider increasing it to at least 12 slots, even this would still be significantly smaller than the Teamspeak 3 free limit of 32 slots but at least slightly more reasonable.

We wouldn’t mind paying a small fee for a higher slot count, had paid for several Teamspeak 3 licences in the past, and in fact already did pay for and try a month of one of the official Teamspeak community servers but found the website interface very clunky, experienced frequent connection issues, didn’t like the lack of customisation, had trouble setting up custom domains, and preferred to keep our data on our own servers, which all lead us to hoping we’d be able to use this server beta.

If you’re serious about getting good testing and feedback at this stage of development please consider increasing the slot limit at least a little, especially while there isn’t even any way to pay for a license at all.

2 Likes

The setup went smooth.
I kinda overshot on the VM, but I was too excited to try it out :smiley:
6 Core 16gig ram, but minecraft is also running on it.

Anyhow, yada yada 5 slots bad, we all hope for more nothing to add here.

I tested the screenshare with cam, worked smoothly for a short test.
Tested: source, 60 FPS, with cam, and demo hero in DotA.

Will test in the upcomming days.
Personally, I am not a fan of the new UI, but lets see maybe there will be some themes to make it look great (TS3) again :smiley:

1 Like

Thanks, I’m struggling to find that setting anywhere to be honest.

Well, got me and 4 friends on for the evening, convinced them all to download TeamSpeak and login. Again, credit where credit is due, voice quality, spot on, latency, miles better than the competition, easy to mute, move channels, turn the volume up/down on individuals, all that good stuff, working well.

Screensharing to, working well, seems reliable, decent enough quality, everyone (all five of us) can watch with no issues, it’s pretty easy.

Customising the server and bits, I can find most of it, just a lot of it is bizarre by today’s standards, why are icon default file limits 8kb for example? What a strange default considering it’s 2025, not 2004. Why do I need to use a URL for the banner? Why not just give me the option to upload an image like you do with icons? Very odd.

Then there’s the big elephant in the room, Persistent chat for channels, it’s almost like it’s been 10 years since Discord released and nobody understands why it tookover so quickly. It’s the social element, being able to see chat history allows you to join in on conversations, catch up on memes or share some yourself for others to read later.

TeamSpeak just doesn’t do social very well, no persistent server hosted channel chats, no server hosted attachments, no pinned comments, No “reactions”, No embeded previews for links.

But, after coming back to TeamSpeak after all this time (I think 6-7 years myself) I’m completely dumbfounded, what has been done in that time? Discord turned 10 years old a few months back. You have this huge opportunity here to really take a chunk of communities away from Discord, but there seems to be a complete lack of understanding why people pick Discord over TeamSpeak, regardless of the worse voice performance.

4 Likes

What is the PID/user that the server runs as in docker? I am trying to bind the /var/tsserver and it’s failing with bad permissions while trying to create the logs folder, and the environmental variable to change the PID does nothing.

1 Like

Thank you! Got it working in ROS

Ok, I ran the Server with podman. So far, pretty nice, permission are a bit wonky, It picks a correct subuid and subgid, but can’t write in a folder exposed from the user running the container.

Quick workaround for anyone interested, sudo chmod 0777 the folder you expose, start the server real quick for it to create the files and shut it down again. Get the UID and GID used inside the folder for the files the server just created. sudo chown UID:GID and sudo chmod 0755 and you are done, should work now. You can’t edit files inside with the normal user right now, but either just do it with root, or have a look at rootlesskit or some other method, there are a few options depending on your setup.

Otherwise works flawlessly. I would very much like the option for socket activation in the future, since rootless containers can’t get the IP of the connected user with pasta as network tho.

2 Likes

I am kind of shocked about this release. 5 slots and almost nothing new?
I am running a small community for so many years and we love(d) TeamSpeak 3 but it’s really hard…
We end up switching to discord here and there because of missing features and everyone uninstalled the new ts client ui immediately since it’s almost unusable. Are you even testing for usability?
Don’t get me wrong, I/we supported TeamSpeak for so many years now but this release and your management decisions are leaving us speechless.
Meanwhile there is discord which evolves rapidly (and you had the chance to get communities to switch back), matrix etc…

2 Likes

changing the whole folder to 9987 worked for me.

but yeah, if you use mapping instead of a separate volume it might be a bug, that the container is not allowed to create a folder unless the target folder is 9987, next thing it will get worried about is the other “file” folder and the two txt files.

I started the server on my server after struggling with file rights since I use bind mounts it started up and works fine for just voice, but I get an I/O error when I try to upload any file. There are no logs regarding this error. I have to say that I don’t use the default file transfer port since that’s used by my TS3Server and I configured port 30034 for file transfer.

I enabled in the client all logs for the server but seems to have no effects.

2025-07-02 07:57:07.653021|INFO    |ServerLibPriv |   |TeamSpeak Server v6.0.0-beta3 (2025-07-01 14:22:02)
2025-07-02 07:57:07.740388|INFO    |ServerLibPriv |   |SystemInformation: Linux 5.15.0-143-generic #153-Ubuntu SMP Fri Jun 13 19:10:45 UTC 2025 x86_64 Binary: 64bit
2025-07-02 07:57:07.740772|INFO    |              |   |checking database integrity (may take a while)
2025-07-02 07:57:07.748837|WARNING |Accounting    |   |Unable to open /var/tsserver/licensekey.dat
2025-07-02 07:57:07.749125|INFO    |Accounting    |   |Licensing Information
2025-07-02 07:57:07.749145|INFO    |Accounting    |   |licensed to       : TeamSpeak Systems GmbH
2025-07-02 07:57:07.749157|INFO    |Accounting    |   |type              : No License
2025-07-02 07:57:07.749173|INFO    |Accounting    |   |starting date     : Tue Apr  1 00:00:00 2025
2025-07-02 07:57:07.749185|INFO    |Accounting    |   |ending date       : Mon Jan 19 00:00:00 2026
2025-07-02 07:57:07.749197|INFO    |Accounting    |   |max virtualservers: 1
2025-07-02 07:57:07.749208|INFO    |Accounting    |   |max slots         : 5
2025-07-02 07:57:07.815287|INFO    |              |   |Precomputing puzzle, this may take some seconds...
2025-07-02 07:57:08.787826|INFO    |              |   |Puzzle precompute time: 972
2025-07-02 07:57:08.788069|INFO    |FileManager   |   |listening on 0.0.0.0:30034
2025-07-02 07:57:08.788488|INFO    |Query         |   |Using a query thread pool size of 2
2025-07-02 07:57:08.793604|INFO    |CIDRManager   |   |updated query_ip_allowlist ips: 172.17.0.0/16, 172.18.0.0/16, 172.19.0.0/16, 172.20.0.0/16, 172.21.0.0/16, 172.22.0.0/16, 172.23.0.0/16,
2025-07-02 07:57:09.307134|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated

Also you mentioned S3 support for file uploads. Do you have a documentation about that? I couldn’t find any config keys regarding this for the environment.

Edit: File transfer works with TS3 Client but not TS6 client on macOS and Windows.

UID: 9987
GID: 9987

With the complete absence of updates, fixes, and the implementation of long-planned features, the news that a TS6 server beta was being released actually inspired some optimism for the project. Honestly, it felt like maybe, finally, something would happen. We could slowly start migrating to the new version, and who knows, maybe after all this time, they would even update the client? I never thought I’d be writing something like this instead of the glowing praise I expected to share for some long-awaited, visible changes.

But to be specific, there are no real changes here. I partly understand the logic: it’s likely the same person making one bad decision after another, dragging the project to the bottom. But how long can you try to cash in on selling poorly functioning community servers before the whole project sinks? It’s gotten to the point where the 5-slot limit for a “beta version” wasn’t fixed immediately.

Or am I the only one who sees this limitation as an obvious problem? The ability to host a server with a broadcast button is functionally the same as renting a community server. If you don’t want to compete with your own revenue stream, then make an effort - offer a real service, don’t just cripple everything in the hopes that someone will believe the coveted paid button will work better.

Is it really that hard to see that the project is still surrounded by tons of enthusiasts who could help revive it, especially on the backdrop of a declining Discord? You can make money later - if updates don’t come out once every five years. Right now, it seems you need to invest. Or am I wrong?

All that the release of the beta server files brought was a working peer-to-peer broadcast button. It’s not even clear why this feature needs a server, since everyone was expecting either improved P2P or proper server-based broadcasting. And how much time has passed? To put a slot limit on such a meager feature… I can’t even take it seriously enough to comment on it. It’s surreal.

I’ve completely lost faith in the project, and I think many others have too. The good old TS3 servers are sufficient to wait things out for a while; there’s no point in waiting for a decent TS6 with these kinds of decisions and at this pace.

I think everyone understands that as soon as a real competitor to Discord appears on the market (and sooner or later, it will) - whether it’s a new solution that responds to user demands or even just improved chats in Steam, it doesn’t matter - it will overshadow and bury TeamSpeak for good. Time was on your side, and you completely failed to use it. It’s better to invest my emotions and money in something else.

And by the way, I think if you didn’t treat your community like fools, you would have raised far more funds for development through donations than you ever will by selling small community servers where even the advertised features work poorly.

11 Likes

I completely agree with you. As a TeamSpeak user since TS1 (2001), I feel absolutely betrayed and misled.

It’s painfully obvious that artificial limitations are being used to push their own hosting services to the forefront in order to generate more revenue. There’s a clear attempt to deceive self-hosters and gradually force them into using TeamSpeak’s official hosting.

This is already evident from this post (TS6 BETA | Community Update & Insights), where they promote the 64-slot servers in their own hosting while claiming to “listen to the community.” But when you ask why the beta server is limited to 5 slots, there’s no real answer—just evasive statements.

TeamSpeak is dead. The developers are trying to troll us with a rebranded TS3 server while luring us into their own hosting model.

2 Likes

For now, this slot limit looks like some kind of sick joke. Besides, what are we supposed to test if nothing has changed from the community servers and your official ones. I can confidently say that most self-hosted server owners are looking for screensharing through the server itself to test, not P2P.

On January 23rd the following words were said “Self-hosting is a core feature of TeamSpeak” - just sayin, about those slots.

5 Likes

If I explain my situation with my friends. We’ve been using TeamSpeak since 2005/2006, last year most of my friends decided to start using Discord. I was hosting server and we really liked performance, because we could rely on my server’s performance.

Now most of them decided to start using only Discord, because there is so many disadvantages in TeamSpeak at the moment. I understand totally that TeamSpeak is a company and needs to make profit to exist, that’s clear and normal.

But problem is, TeamSpeak app is obsolete with a ton of limitation and disadvantages if you compare these 2 programs. I would not pay license for TeamSpeak server, if it doesn’t support p2s screenshare, mobile apps work bad and don’t support video chat / screenshare, file / attachments are working bad and are limited to 5 MB, chat is going thro their’s servers, …

This is not message to current developers, I support them and wish them the best, but management and CEO of TeamSpeak need to realize that they need more DEVs this moment, they won’t survive with that small team, and I repeat AGAIN, it’s not DEVs fault but management’s one. I know that a few devs can’t do miracles.

My personal opinion about everything is, TeamSpeak needs:

  • TeamSpeak 6 server with full support (peer-to-server screenshare / video, chat should be server sided - if it’s self hosted)
  • New mobile apps (iOS and Android with full support of sending media and reactions etc., screenshare + video call)
  • UX / UI improvements, sending links, media, editing message etc. need improvements by modern standards, if you don’t have local specialists, you outsource it, simple.
  • Option as admin, if chat should be stored on server or only delivered for online users (it could be setting in the channel)

If company delivers good product, there is no problem with paying license and supporting project. Most of us have feeling that current TeamSpeak 6 server is a minor upgrade from TeamSpeak 3 server, they added option of p2p screenshare, otherwise everything except slots is the same.

Since TeamSpeak 6 release client didn’t receive single update from january, we really can’t be optimistic about the future, if we can’t use p2s screenshare which is kind of basic functionality, when can we expect new mobile apps, if you ask me, never.

I want to be honest and I repeat, this is not attack on @SYOX @LeonMarcelHD or anyone else, guys are doing their’s best, community’s frustractions should be forwarded to management, they need to make moves, with small team like that, project simply won’t survive and I think that’s clear from the plane.

9 Likes

I don’t fully believe this is a matter of indirectly promoting their Community service, as even that one has missing features we’ve been expecting with the server release such as the streaming still being peer to peer. So it’s a common limitation.

The 5 slot limit is… a different matter. I think the biggest offender by far was not setting expectations in check beforehand.

Anyhow, I’m more interested in the client getting Wayland fixes before any server-side features being finally implemented, probably won’t return to the forum until the next client update is out.

3 Likes

No one claimed that the lack of server-side screen sharing is being used as leverage — rather, it’s the user limit that’s being used for that. This decision is simply completely incomprehensible to me, but the biggest issue I have with it is the total lack of communication regarding the reasoning behind it.

I’ve asked about it through several channels and would genuinely like an explanation as to why this decision was made. But this question is consistently avoided, and therefore I assume malicious and deceitful intent behind it. It’s as simple as that.

1 Like