The issue was that there was no query_ssh_ip/query_ssh_port variable set in the config.
Apologies for the oversight, this can be ignored.
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
Type: Posts; User: Revenge282; Keyword(s):
The issue was that there was no query_ssh_ip/query_ssh_port variable set in the config.
Apologies for the oversight, this can be ignored.
I've noticed this issue with 3.4.0 and 3.5.0 on Debian x64. It may have existed prior as well.
Set in the ini as well as the config is the query_ip=1.2.3.4
netstat -lntp shows ts3 is bound to...
I had it set to 192.168.1.143, as that is what the voice_ip and query_ip are set to as well, and they worked. Setting it to 0.0.0.0 did work though.
Thanks.
I am having the same issue. As far as server query and the actual voice server goes, it's working fine. But anything to do with 30033 is not working. I do have everything forwarded through my...
I agree that this authentication system is very strange compared to the common and widely accepted methods. I would, however, like to see the previous type of authentication as at least a secondary...
I think that the TS2 user verification and registration system was perfect. However, I do like the current idea of the permission system now, but it needs to be reworked to a simpler interface. As...
My main confusion comes from the Power system. Is it ran as a type of immunity system as in Ventrilo, or is it related to the security levels that a client accumulates? I have based my permissions...