@TS.ChrisR working perfect. Thank you for this fast Update. 
4 Likes
Hello,
since the upgrade to teamspeak server 3.13.5 on my linux VPS i have issues with serverquery.
Usually i control my teamspeak server with YatQa and after the upgrade to 3.13.5 i was able to connect to the server just as usual for the first 2-3 times but after that i can`t establish any connection at all and i need to restart my server instance (systemctl restart…) and it works for a couple of times, before it fails again.
At first i thought the error might be in YatQa but i double checked it with TS3 Manager and it shows the exact same behavior. I can connect when the server just came up online for 2-3 times but after that, the connection
query_protocol is set to ssh in my ts3server.ini and i am using a non default port as a query port.
It worked always fine and the only difference is the recent upgrade to 3.13.5.
Did anyone of you experienced something similar?
1 Like
Thanks for sharing. I will upgrade in the night hours and let you know if the problem still persists.
2 Likes
Also wanted to chime in and say that one ATP directly told me to buy a whitelist slot since they know that the recent changes lead to nearly everything getting blocked.
I can simply connect via YATQA and get blocked if I reconnect in that moment.
Is there already a date when approximately this version will be released as stable?
1 Like
Beta next week. Stable has no date.
Maybe we skip beta but this needs to be discussed first.
7 Likes
@blowoffsteam @LeiToH @Karazhan @antipen44 @fabm3n @Eiki @tatayer @olokos @XeroX @FakE @TheChaosToast
Is the issue fixed for you with the 3.13.6-experimental1 ?
http://files.teamspeak-services.com/pre_releases/server/3.13.6-experimental1/
6 Likes
Yes after the update i removed all entrys from my query_ip_allowlist.txt and all of my scripts are still working and can connect to the server over raw query.
2 Likes
Hello, after a few days of use I have no more problems, so I will say yes the problem is solved.
cordially
2 Likes
In my case on version 3.13.5 there are no issues with serverquery bans at all.
I know for a fact that I have a script running and doing a lot of serverquery calls (reasonably of course, but quite often) and no bans are done, everything goes smoothly, I think so at least.
Gametracker also works great among other websites in the whitelisted IPs.
If possible in the next update, please make a possibility to automatically accept queries from all IPs as an option in config maybe.
This way we wouldn’t have to go through a tedious process of adding every ts3 ranking website IPs to the whitelist, exactly as it was possible before the 3.13 updates
YatQA is also working fine for me despite not being in whitelist, but remote anonymous site do get blocked by not having their IPs in the whitelist, sadly.
I’m happy stuff is being moved forwards, and fingers crossed this could be introduced to make server admins like easier, like it always has been.
Thanks and please read my post! <3
A setting won’t come.
But if you want all IP’s to be accepted add 0.0.0.0/0 to the list.
But doing this is risky since now nothing is blocked any longer.
5 Likes
sorry for not answering before @TS.ChrisR . I have no time, in the same way I am using 3.15.5 with the ips of all the queries added since each ranking page provides them and it has been working excellent since the day of the update, I will wait for the stable .6 and I will update many thanks for the Quick answers and solutions that you gave us with this topic
1 Like
No solution here is working for me. I will downgrade and wait for a version that works.
In that case your issue is not the same one as other’s if even the IP in allowlist did not change anything.
5 Likes
I dont have any kind of Problem, when i Update/ Upgrade my Server with and without a license. All here is working fine for me. I dont know what is wrong with this version? 
My answer just said the problem the people have here is not the same when adding the IP to allowlist did not fix the issue. AND NOTHING ELSE
From code perspective we found exactly what caused this and when the workaround (we know it must work) did not work from you then your issue is not the same.
There won’t be any other version with related fixes when we do not know what caused your issue.and as long the only information we have is “it does not work”. Please give us details anything in the log or steps to reproduce or anything else that could help.
5 Likes
