The WebQuery port breaks after a few requests

[aramperes]

Using TeamSpeak 6.0.0.beta6 server. I am trying to migrate an application that made use of the telnet Server Query endpoint.

After 5 requests to the WebQuery port (10080), it will stop replying. It closes any new request with no response. Server restart fixes it (for 5 more requests).

$ curl -H 'x-api-key: ***' http://192.168.1.110:10080/1/channellist
{"body":[{"channel_name":"Default Channel","channel_needed_subscribe_power":"0","channel_order":"0","cid":"1","pid":"0","total_clients":"2"}],"status":{"code":0,"message":"ok"}}

$ curl -H 'x-api-key: ***' http://192.168.1.110:10080/1/channellist
{"body":[{"channel_name":"Default Channel","channel_needed_subscribe_power":"0","channel_order":"0","cid":"1","pid":"0","total_clients":"2"}],"status":{"code":0,"message":"ok"}}

$ curl -H 'x-api-key: ***' http://192.168.1.110:10080/1/channellist
{"body":[{"channel_name":"Default Channel","channel_needed_subscribe_power":"0","channel_order":"0","cid":"1","pid":"0","total_clients":"2"}],"status":{"code":0,"message":"ok"}}

$ curl -H 'x-api-key: ***' http://192.168.1.110:10080/1/channellist
{"body":[{"channel_name":"Default Channel","channel_needed_subscribe_power":"0","channel_order":"0","cid":"1","pid":"0","total_clients":"2"}],"status":{"code":0,"message":"ok"}}

$ curl -H 'x-api-key: ***' http://192.168.1.110:10080/1/channellist
curl: (52) Empty reply from server

No logs in the TS6 server.

Compose file:

services:
  teamspeak:
    image: docker.io/teamspeaksystems/teamspeak6-server:latest
    container_name: ts6
    restart: always
    ports:
      - "9987:9987/udp"   # Voice Port
      - "30033:30033/tcp" # File Transfer
      - "10080:10080/tcp" # Web Query
      - "10022:10022/tcp" # SSH Query
    environment:
      - TSSERVER_LICENSE_ACCEPTED=accept
      - TSSERVER_QUERY_SSH_ENABLED=true
      - TSSERVER_QUERY_HTTP_ENABLED=true
      - TSSERVER_QUERY_SSH_PORT=10022
      - TSSERVER_QUERY_HTTP_PORT=10080
      - TSSERVER_QUERY_SKIP_BRUTE_FORCE_CHECK=true
      - TSSERVER_QUERY_LOG_COMMANDS=true
    volumes:
      - /data:/var/tsserver/:U

[aramperes]

The SSH server behaves similarly after 5 connection attempts. I think it might be the brute-force detection kicking in, but it is ignoring my setting TSSERVER_QUERY_SKIP_BRUTE_FORCE_CHECK=true if so.

[HuppiN]

Thank you for your report!

While debugging, I identified an issue in the HTTP connection cleanup routine that is causing this behavior. As a temporary workaround, you can make use of the whitelist feature.