That’s incorrect, TSViewer triggers the default spam protection since ever.
As long as you didn’t change the default instance parameters the IP will get banned temporarily.
The TSViewer is sending 6 commands to the TeamSpeak server when querying it and is evaluating the response values. Out of this values he generates the TSViewer tree. The TS3 server has a flood protection […]
For the IP address of my server (TSViewer) there must be made an exception. The default values of the flood ban protection are so low, that the TSViewer queries are interpreted wrongly as an flood attack.
These guidelines are a few years old already.
Your TeamSpeak server’s default settings will cause a temporarily ban - always.
I’m using the service, too for a lot of years now and it always has been required to whitelist the IP.
The default instance flood parameters haven’t been touched the last server updates.
Yes and no.
If there’s no whitelist/blacklist file already the server will generate these two now with the new names.
If you’re already using a
ts3server.ini configuration file on the startup the server will use the files being defined as parameters - if they exist of course - or will generate them by the name(s) defined in your
Due to how configuration/initialization files work you can also use multiple whitelists/blacklists if you want to.
Newer TeamSpeak server version will read and support both file names by default.
Doing it by hand, for example: