Hi, great job, thanks! Please tell me how to fix the error:
It feels like the serveradmin doesn’t really have access rights to the instance in the TS database. Is there a solution?
looks like the server query is not able to join a client in the server to acces the data due to insufficient permissions. 
Yes, that’s right. But the rights are there, the API has been received. Will only reinstalling help?
you using the docker images or do you build from source?
I’m using the official Docker image: teamspeaksystems/teamspeak6-server:latest
I’m using the official Docker image teamspeaksystems/teamspeak6-server:latest. The serveradmin account seems to have lost its instance-level permissions. Even when connecting via SSH query (use sid=0) and trying to run instanceinfo or serverlist, I get error 2568 with failed_permission=b_serverinstance_virtualserver_list.
I have a valid WebQuery API key (created with sid=0), but it also returns the same error 2568. The TS6 Manager dashboard shows “No server selected” because of this.
I tried recreating the Docker container, but the permissions were not restored since the data volume (ts6_data) was preserved. Is there a way to fix serveradmin instance permissions without wiping the volume and losing all server data (channels, groups, clients)?
FIXED.
The issue was a missing permission in the TS6 SQLite database. The b_serverinstance_virtualserver_list permission was completely absent from the perm_server_group table for any group.
The fix was to manually insert it for the Server Admin group (id=3, server_id=0):
sql
INSERT INTO perm_server_group (server_id, id1, id2, perm_id, perm_value, perm_negated, perm_skip)
VALUES (0, 3, 0, 'b_serverinstance_virtualserver_list', 1, 0, 0);
After restarting the TeamSpeak container, everything started working. Not sure how this permission got removed — possibly related to container recreation or multiple serveradmin password changes.
1 Like
I tried deploying ts-manager and found it exceptionally useful. But can Chinese language be added? Thank you very much.
UPDATE:
The MusicBot can now also stream video content from YT or (almost) any direct media link on the web.
This feature is in bloody beta right now and bugs/performance issues are likely.
3 Likes
this looks like a great project! love the idea of an integrated music bot. is there also an option to subscribe so it whispers me the music?
this would be an idea for a feature. 
Do you can open an issue for a feature request on github?
1 Like
what do i miss 
i try the new option for self signed certs.
but it not connect …..
#- TS_ALLOW_SELF_SIGNED=${TS_ALLOW_SELF_SIGNED:-false}
#- TS_ALLOW_SELF_SIGNED=${TS_ALLOW_SELF_SIGNED:-true}
- NODE_TLS_REJECT_UNAUTHORIZED=0
only working with my line : - NODE_TLS_REJECT_UNAUTHORIZED=0
I’ve tried several videos and keep getting “timeout of 15000ms exceeded”
update ytdl inside the docker
ytdlp auto update · Issue #36 · clusterzx/ts6-manager
1 Like
This project looks really cool! 
Any plans on adding support for pterodactyl egg?
It’s on the latest version
Subject: Customizing the Query Bot nickname in Flows
Hello,
First of all, congratulations on the amazing work accomplished with this manager!
I have a question regarding the serveradmin bot that sends messages to clients via the Flow engine. Is it possible to change its nickname to a custom name (e.g., “myts6Bot”) so that users don’t see “serveradmin” in the chat?
If so, what is the best practice to achieve this? I have tried using a WebQuery node with the command clientupdate client_nickname=MyBotName, but it doesn’t seem to update the sender’s identity for the following Send Message nodes.
Thank you for your help!
If you mean 15000ms exceed error in the Manager UI, then this is propably because ICE for Web-preview doesnt „Connect“ fast enough. Joining the Stream should work and reloading the page should then give you a proper preview.
But I am currently on some „experiments“ for the VideoBot and maybe this will be fixed along with it. - but I still need some time to test my experiments to not Roll out any „trash“ 
My issue is that the stream doesn’t even start for me in the first place.
Can you maybe open an Issue for that on GitHub? 
Can you also Open an Issue on github and provide backend Logs and Sidecar Logs?