Getting a virus flag on the files for beta4 windows binaries
i am assuming its a false positive, buut pays to check
@ Maki4748’s post fixed podman for me. Here is the podman-compose.yml file I’m using with rootless podman on RHEL 9:
version: "3.8"
services:
teamspeak:
image: teamspeaksystems/teamspeak6-server:latest
container_name: teamspeak-server
restart: unless-stopped
# ports:
# - "9987:9987/udp" # Voice Port
# - "30033:30033/tcp" # File Transfer
# - "10080:10080/tcp" # Web Query
network_mode: host
environment:
- TSSERVER_LICENSE_ACCEPTED=accept
volumes:
- /your/directory/here:/var/tsserver:Z
volumes:
teamspeak-data:
I have network_mode: host there, allowing me to port forward on the firewall side
1 Like
Dont understand why you guys are so keen to burn all trust and faith from you long time & newly arrived users, making essentially discord but without the benefits of anything besides bulk billing vs nitro… (Communities is what im talking about), you had lots of features for your own hosted communities and billing before the system was even tested being over provisioned (No error messages on the web portal as if you didnt think to check theres availability).
You then after 6+ months of people saying WTF you lied, you still keep saying on twitter that your the best and ignoring all the issues being raised, you then come up with this “Weve been working on packaging the server files and after a long wait its finally coming” to which you then put together what was essentially TS3 with p2p sharing and some matching up of sql queries+data so that it would reference any new naming in ts6 client.
It seems that you guys worried that after your bull**** communities release and massive twitter rug pull, plus every reddit and forum post involving teamspeak saying you still havnt made true to releasing an upgraded teamspeak with the same fundamentals of self control/hosting/standalone… its like you guys wanted to make a huge splash so youd get bought out or massively funded by someone who wanted to take a slice of discords market share for a piece of the spying, restricting, emoji selling no choice platform.
But so far youve just tested the patience of your most avid users while operating in bad faith, made the generation who only knows discord further believe its the best and not gotten yourself a big buyout.
Tell everyone in your twitter posts that you got carried away, specific stuff is missing, your prioritising communities and your ecosystem over supplying software thats not linked to your infrastructure for core operations only needing license verification.
Tell everyone that you made a mistake listing features to be released just days prior to release and why that happened, acknowledge it was misleading.
Thats my rant, also how do i refund the communities servers i purchased but couldnt be provisioned.
Imagine if you had a true TS3 to Teamspeak 6 with everything contained in the server and offline clients, you couldve made a case that the privacy and ability to close it off to avoid unwanted connections and any sharing of everything your talking about makes it a good alternative for education sector use, an alternative for corporate devices as ive experienced many times in the past efforts to completely eradicate discord being used on devices following security uplifts due to the fact that its tracking far too much to not garauntee that confidential and classified information is captured.
1 Like
You could thank the developers for increasing the slot limit beyond five, but… for only two months? Seriously? Now everything is starting to make sense. What’s not clear is when the rest of the active community will figure this out, and once they do, I have no idea how you plan on returning to the market, let alone trying to sell servers.
Here’s the most important takeaway: proper self-hosting is gone for good. It seems the basic “free” license will be stripped down to a demo version simply to justify the purchase of a community server. The surprise is that these community servers don’t provide the experience that has kept TeamSpeak relevant and afloat all this time. So, it’s baffling why an average, casual user who just wants a turnkey solution would bring their money here instead of to Discord, which, by the way, doesn’t limit its core functionality at all.
By competing with your own solutions, misleading your community - and most of the time, completely ignoring it with no updates for at least half a year - you’ve forgotten that your main competitor isn’t the community that tried to keep the project alive through word-of-mouth, precisely because they could host their own servers however and wherever they wanted. Your main competitor is Discord, whose basic free service completely outclasses any of your PAID features, even if we include all the promised fairy tales (which we’ll likely be waiting years for anyway). This is madness!
An average user who doesn’t know how to self-host or manage servers won’t care about some imaginary promise of privacy and security. They will just go to Discord, create a server for their community in two clicks, and use it with almost no restrictions and with stable features that already surpass TeamSpeak’s paid communities.
Frankly, this is just sad. I don’t understand the logic. I would have been willing to pay a fair price for a proper license because your community server locations are not suitable for me. I think many others would support me in this. If you had released a client update that fixed P2P streaming, hardware acceleration, and other UX/UI flaws like the chat problems - I would have gladly, WITHOUT HESITATION, IN ADVANCE, ON FAITH, paid for a lifetime license or even agreed to a subscription model to support the developers in bringing the product to a finished state.
But instead, you treat us like fools, make up excuses, and worry about short-term profit on an unfinished product instead of actually thinking about the future - a future that remains completely unknown because there is still no news and no roadmap. What is there left to believe in?
This is a strategic failure and a complete misunderstanding of your community and the very people who make your project’s existence possible. If it weren’t for the geeks who set up their first TeamSpeak servers to chat with friends decades ago, no one would have paid you any attention, not even from your cringey posts on Twitter.
Public support, word-of-mouth, a loyal community - these are things that even vast sums of money cannot buy. I hope you realize what you were gambling with each time and, in the end, it seems you have finally lost. It was a priceless asset, something Discord could only envy. But now, even I - someone who wrote a custom bot for TS3 with features that TS6 will probably never have - have started to consider paying for Discord again.
9 Likes
Thank you, first of all. Since the announcement that you would take a bit more time to share news about the various development stages, you have been much more responsive, and it’s nice to have been heard. So, thank you!
Now, you have probably noticed that everyone has questions about this limited slots issue. I understand that you need funding for TeamSpeak’s development, and everything will depend on the prices you offer for server licenses. However, aiming for only 5 available slots for the self-hosted version is a bit tight… Thanks anyway for allowing the option to have more slots temporarily on the beta version.
Regarding the features, I haven’t been able to test them in detail yet, but it seems to align with TS3 and be relatively stable. Indeed, there is no server screen sharing, only P2P for now, but I can’t criticize; it’s just a beta. The latency and stability are excellent on a local network. However, I noticed that it takes a bit of time to connect from an external network. I thought it might be a problem with my infrastructure, but my other services are much more responsive. So, there might be something to look into on that side.
Finally, I have a technical question. Since TeamSpeak 6 is based on Synapse, Element (Matrix) has developed Element Call, which is a separate instance of Synapse but still uses the homeserver for authentication, encryption, events, etc.
So, why not do something similar? I already have a Matrix instance running; I would have loved to integrate a TeamSpeak call server to replace Element Call on my instance!
I don’t know the current operation in detail, but it seems that the TeamSpeak Synapse instance is required in addition to the self-hosted voice server instance to function. So, will we be able to have this integration in the future?
In any case, thank you for sharing a beta version of the server with us. Good luck with the development. I know it’s complicated to meet everyone’s expectations, especially for a small team 
1 Like
Stoked about the beta, is there any way to run the client without the need to create an account? Some of my users would just like to be able to directly connect and I was curious if that was possible / planned.
What is the minimum version required to connect to the server? and is it possible to change it?
I am finally getting around to testing the Beta server and wanted to know if its possible for me to stand this up next to my teamspeak 3 server. I am assuming I should be able to change the port numbers so that way my production server and test server can both be up at the same time.
Apparently it’s planned, but atm you can’t with TS6 Client. However you can still use TS3 client to connect to TS6 server which does not require an account to connect to a server.
it’s possible. I started testing it today. I just changed the ports in the config
Is this going to be paid fully when it gets released, or It’s going to be like the way how TeamSpeak 3 servers work?
I suggest saving the text chat of channels on the server side instead of the client side, with an auto-clear feature after X days
1 Like
Are there plans to support ARM architecture?
1 Like
You can run it on arm with docker compose by adding
services:
teamspeak:
...
platform: linux/amd64
...
Everyone was criticizing the 5 slot limit and probably I’m the only one that saw that as a correct number. I pay for a server license already and even tho I try to work with my social skills my community doesn’t go above 5 majority of the times, maybe if they included the +1 bonus thing I would like it better, but yeah… Majority of the communities were talking about higher numbers, but people coming to the server don’t surpass 5 majority of the times.
I think their decision to have 5 slots instead were pretty much based in statistics more than anything, you probably are the exception in the case, but I saw many new people that joins Teamspeak these days goes with a group of 2 or even 3 and that’s it. Now if you made a community for quite some time already on Teamspeak I would feel bad as well, but this initial beta clearly wasn’t targeting the big communities so really I don’t understand why people was rage baiting that much.
1 Like
Nice of you to presume to speak for everyone else.
I think you didn’t understand the reasoning behind this decision — and it’s not even the decision itself that makes me so angry, but rather the way it was communicated.
I, as well as others here, asked very directly multiple times what would happen with the slot limit after the beta, and all of those questions were consistently ignored!
That’s just absolutely disgusting behavior, and I still refuse to test the beta server.
Let them do whatever they want — I’m not playing along with this nonsense.
3 Likes
You seem to be missing the point of the BETA release entirely, the beta release is NOT intended to be an actual server you run for your community, it’s to test the functionality while it is fully fleshed out.
32 User license for 2 months should be more than enough to load test and give the BETA a workout.
I mean, seriously? it’s a BETA. Cool off a bit.
4 Likes
Thx 
1 Like
Just wanted to update -
Server running in docker (ubuntu server, x86)
Deployed the example MariaDB with portainer, all working well (didn’t bother setting the volumes differently yet)
Connected just fine, managed to get my key and take ownership of the server and currently testing screen share locally (from a windows device to linux) and it is working great with the P2P mode
I have also connected from the TS3 mobile client, and it worked about as well as the TS3 mobile client normally works
So far the only crucial things that are missing are; Server side storage for text channels and Server-based screen share, but I think these have been mentioned already
Waiting for some more friends to come online, but so far, really liking it!
Thanks for all the hard work TS team, I am really looking forward to more developments!
7 Likes
Guys, can you tell me how to migrate my old ts3 server settings (ACLs, chanels etc)?
