search

TheHolyWaffle / TeamSpeak-3-Java-API

A Java wrapper of TeamSpeak's 3 server query API.
MIT License
306 stars 107 forks source link

Command whoami was not answered in time. #56

Closed robingenz closed 5 years ago

robingenz commented 9 years ago

I wrote a bot for my TS3 server with the aid of this API (using the latest version). Unfortunately, the bot stopped working after a few hours. Eclipse stated the following errors:

Quellcode:

[2015-08-19 05:23:16.226] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:24:13.427] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:24:54.731] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:25:24.537] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:25:45.457] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:27:05.736] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:27:40.187] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:28:25.802] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:29:04.861] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:29:48.444] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:30:24.972] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:30:56.959] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:31:34.193] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:32:08.505] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:33:17.209] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:34:14.566] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:35:09.354] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:35:50.669] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:37:16.662] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:38:00.100] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:38:48.177] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:39:15.655] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:39:24.745] [SEVERE] Command clientinfo was not answered in time.
[2015-08-19 05:40:22.120] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:41:28.145] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:42:02.504] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:43:10.602] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:43:44.876] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:44:41.985] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:45:09.403] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:45:48.287] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:46:50.047] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:47:24.156] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:48:14.432] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:48:39.393] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:49:06.975] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:50:10.652] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:51:17.092] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:51:58.404] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:52:39.522] [SEVERE] Command clientinfo was not answered in time.
[2015-08-19 05:52:39.522] [SEVERE] Command whoami was not answered in time.
[2015-08-19 05:53:52.325] [SEVERE] Command whoami was not answered in time.
[2015-08-19 06:06:41.579] [SEVERE] Command clientinfo was not answered in time.
[2015-08-19 06:10:11.419] [SEVERE] Command clientinfo was not answered in time.

The log file of the API showed the following errors (they didn't cause the bot to stop working though):

[2015-08-19 04:53:31.616] [SEVERE] TS3 command error: {id=1281, msg=database empty result set}
[2015-08-19 04:53:57.270] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 04:57:29.073] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 04:57:56.457] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:01:01.964] [SEVERE] TS3 command error: {id=1281, msg=database empty result set}
[2015-08-19 05:01:55.578] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:05:55.014] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:08:28.235] [SEVERE] TS3 command error: {id=1281, msg=database empty result set}
[2015-08-19 05:09:54.569] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:12:02.538] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:13:54.869] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:15:54.650] [SEVERE] TS3 command error: {id=1281, msg=database empty result set}
[2015-08-19 05:17:55.180] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:21:05.503] [SEVERE] TS3 command error: {id=1281, msg=database empty result set}
[2015-08-19 05:21:12.590] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:21:25.642] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}
[2015-08-19 05:21:53.852] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}

I greatly appreciate your help.

TheHolyWaffle commented 9 years ago

It happens when connection has been lost to the TS3 server. Unfortunately, no automatic reconnection system is implemented yet.

2015-08-19 12:42 GMT+02:00 Red0head notifications@github.com:

Last night I had the first test run of my bot, which was written with this API. The API has greatly facilitated the work. Unfortunately, the bot no longer ran this morning. The error started with the following message "Command whoami was not answered in time.". And the bot stopped with this message: "Command clientinfo was not answered in time.".

Quellcode: [2015-08-19 05:23:16.226] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:24:13.427] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:24:54.731] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:25:24.537] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:25:45.457] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:27:05.736] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:27:40.187] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:28:25.802] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:29:04.861] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:29:48.444] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:30:24.972] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:30:56.959] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:31:34.193] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:32:08.505] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:33:17.209] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:34:14.566] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:35:09.354] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:35:50.669] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:37:16.662] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:38:00.100] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:38:48.177] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:39:15.655] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:39:24.745] [SEVERE] Command clientinfo was not answered in time. [2015-08-19 05:40:22.120] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:41:28.145] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:42:02.504] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:43:10.602] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:43:44.876] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:44:41.985] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:45:09.403] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:45:48.287] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:46:50.047] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:47:24.156] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:48:14.432] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:48:39.393] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:49:06.975] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:50:10.652] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:51:17.092] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:51:58.404] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:52:39.522] [SEVERE] Command clientinfo was not answered in time. [2015-08-19 05:52:39.522] [SEVERE] Command whoami was not answered in time. [2015-08-19 05:53:52.325] [SEVERE] Command whoami was not answered in time. [2015-08-19 06:06:41.579] [SEVERE] Command clientinfo was not answered in time. [2015-08-19 06:10:11.419] [SEVERE] Command clientinfo was not answered in time.

Before the bot stopped running i found this lines in the log file (maybe it help), but it doesn't stopped the bot:

[2015-08-19 04:53:31.616] [SEVERE] TS3 command error: {id=1281, msg=database empty result set} [2015-08-19 04:53:57.270] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 04:57:29.073] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 04:57:56.457] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:01:01.964] [SEVERE] TS3 command error: {id=1281, msg=database empty result set} [2015-08-19 05:01:55.578] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:05:55.014] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:08:28.235] [SEVERE] TS3 command error: {id=1281, msg=database empty result set} [2015-08-19 05:09:54.569] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:12:02.538] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:13:54.869] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:15:54.650] [SEVERE] TS3 command error: {id=1281, msg=database empty result set} [2015-08-19 05:17:55.180] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:21:05.503] [SEVERE] TS3 command error: {id=1281, msg=database empty result set} [2015-08-19 05:21:12.590] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:21:25.642] [SEVERE] TS3 command error: {id=512, msg=invalid clientID} [2015-08-19 05:21:53.852] [SEVERE] TS3 command error: {id=512, msg=invalid clientID}

I use the latest version of your API. I hope some of you can help me.

— Reply to this email directly or view it on GitHub https://github.com/TheHolyWaffle/TeamSpeak-3-Java-API/issues/56.

robingenz commented 9 years ago

Why should the bot lost the connection to the server when the server is still online? That's what i don't understand ^^ The server was all the time online and the bot lost the connection...

TheHolyWaffle commented 9 years ago

The server must have gone offline at one point and restarted afterwards.Do you host your own TS3 server? Or do you rent one?

2015-08-20 12:09 GMT+02:00 Red0head notifications@github.com:

Why should the bot lost the connection to the server when the server is still online? That's what i don't understand ^^ The server was all the time online and the bot lost the connection...

— Reply to this email directly or view it on GitHub https://github.com/TheHolyWaffle/TeamSpeak-3-Java-API/issues/56#issuecomment-132964327 .

rogermb commented 9 years ago

Hijacking this thread real quick.

@TheHolyWaffle, could you please catch up on what's going on over at gitter? There's someone offering us a CI solution and he specifically wants to talk to you, as you're the owner of this repository.

robingenz commented 9 years ago

I rent my own server and i log every downtime and i have users who were online for at least 8 hours and the bot lost the connection after 4 hours...

robingenz commented 9 years ago

I deleted the "whoami-process" out of your API and now it works ^^ the bot is online since 16 hours ^^ which function has the command besides of saying "who i am"? Hahaha :D

TheHolyWaffle commented 9 years ago

The whoami command is sent to keep the connection between you and the server stable when you haven't send any commands for a long time.

2015-08-20 19:01 GMT+02:00 Red0head notifications@github.com:

I deleted the "whoami-process" out of your API and now it works ^^ the bot is online since 16 hours ^^ which function has the command besides of saying "who i am"? Hahaha :D

— Reply to this email directly or view it on GitHub https://github.com/TheHolyWaffle/TeamSpeak-3-Java-API/issues/56#issuecomment-133077020 .

robingenz commented 9 years ago

What if i would let the whoami process out of your API and create a thread in my app who request a few information like the client number any 5 minutes for example?

robingenz commented 9 years ago

Btw very good api and nice support you saved me a lot of time :)

TheHolyWaffle commented 9 years ago

What you just described is exactly what happens in the KeepAlive functionality of the api.

Back to your issue, perhaps it must have been you who has lost connection at one point to the server?

2015-08-20 19:49 GMT+02:00 Red0head notifications@github.com:

Btw very good api and nice support you saved me a lot of time :)

— Reply to this email directly or view it on GitHub https://github.com/TheHolyWaffle/TeamSpeak-3-Java-API/issues/56#issuecomment-133095847 .

robingenz commented 9 years ago

Alright i will check this. Would i have any cons when i would replace your "whoami" function with my thread(which send any 5 minutes a command)?

rogermb commented 9 years ago

Well, no, not really. "whoami" is just the command the TS3 API uses as a keepalive. Whether you substitute it or not doesn't really matter; once the connection is interrupted you'll stay disconnected.

robingenz commented 9 years ago

okay i will run the bot and the teamspeak server now on the same server... there he shouldn't loss the connection ... ^^ I'll will get back soon

robingenz commented 9 years ago

So i tested the bot now and the command whoami still "not answered in time". So what can i do now? I run the bot on the same server like the teamspeak ... He can't lose the connection (i mean it's the same server...) :/

Kakifrucht commented 9 years ago

This shouldn't be happening, I use this API without any restarts for many months straight and there are no issues whatsoever. If you run locally try setting the FloodRate.UNLIMITED in the TS3Config object.

robingenz commented 9 years ago

I know. I can't understand it why it didn't work for me. I still set the floodRate unlimited :/ What version did you used?

Kakifrucht commented 9 years ago

I'm currently on the latest build, however the linked stable one worked fine aswell.

robingenz commented 9 years ago

okay, i will try it again. But since yesterday i have a second problem. I didn't changed anything in my code and after ~5 hours of running the bot he stopped with this error message: "Socket Reader has stopped". What should I do?

rogermb commented 9 years ago

Was there a stack trace or anything else "unusual" in the log right before that?

rogermb commented 9 years ago

Something else I noticed is that the timestamps in your log are weird. Usually, the "whoami" commands should be exactly one minute apart.

[2015-09-02 13:14:42.349] > login serveradmin password
[2015-09-02 13:14:42.355] [login] < error id=0 msg=ok
[2015-09-02 13:15:42.610] > whoami
[2015-09-02 13:15:42.616] [whoami] < virtualserver_status=unknown virtualserver_unique_identifier virtualserver_port=0 virtualserver_id=0 client_id=0 client_channel_id=0 client_nickname client_database_id=1 client_login_name=serveradmin client_unique_identifier=serveradmin client_origin_server_id=0
[2015-09-02 13:15:42.618] [whoami] < error id=0 msg=ok
[2015-09-02 13:16:42.898] > whoami
[2015-09-02 13:16:42.904] [whoami] < virtualserver_status=unknown virtualserver_unique_identifier virtualserver_port=0 virtualserver_id=0 client_id=0 client_channel_id=0 client_nickname client_database_id=1 client_login_name=serveradmin client_unique_identifier=serveradmin client_origin_server_id=0
[2015-09-02 13:16:42.906] [whoami] < error id=0 msg=ok
[2015-09-02 13:17:43.169] > whoami
[2015-09-02 13:17:43.175] [whoami] < virtualserver_status=unknown virtualserver_unique_identifier virtualserver_port=0 virtualserver_id=0 client_id=0 client_channel_id=0 client_nickname client_database_id=1 client_login_name=serveradmin client_unique_identifier=serveradmin client_origin_server_id=0
[2015-09-02 13:17:43.177] [whoami] < error id=0 msg=ok
[2015-09-02 13:17:57.532] > clientlist -uid -away -voice -times -groups -info -icon -country
[2015-09-02 13:17:57.532] [clientlist] < error id=1024 msg=invalid\sserverID
[2015-09-02 13:17:57.533] [SEVERE] TS3 command error: {msg=invalid serverID, id=1024}
[2015-09-02 13:18:57.789] > whoami
[2015-09-02 13:18:57.795] [whoami] < virtualserver_status=unknown virtualserver_unique_identifier virtualserver_port=0 virtualserver_id=0 client_id=0 client_channel_id=0 client_nickname client_database_id=1 client_login_name=serveradmin client_unique_identifier=serveradmin client_origin_server_id=0
[2015-09-02 13:18:57.795] [whoami] < error id=0 msg=ok
[2015-09-02 13:19:58.058] > whoami
[2015-09-02 13:19:58.065] [whoami] < virtualserver_status=unknown virtualserver_unique_identifier virtualserver_port=0 virtualserver_id=0 client_id=0 client_channel_id=0 client_nickname client_database_id=1 client_login_name=serveradmin client_unique_identifier=serveradmin client_origin_server_id=0
[2015-09-02 13:19:58.065] [whoami] < error id=0 msg=ok

In the log you sent us, there are segments where there's way more than 1 minute between the commands and other ones where there's less than 40 seconds in between.

So I wonder, are you running this API on a single-core machine or are you using this API in an "unconventional" way?

robingenz commented 9 years ago

No nothing. I let the bot run on 3 different machines. My PC (i7 3770), my home server (amd processor 6 cores) and on a virtual server (2v cores) at my hosting provider. On the two servers i use ubuntu 14.04.3 LTS with the "java-default" package and the "java jre8" package. On my pc i let it run in eclipse. I tested it on every machine with a local ts3 server. I don't know what I'm doing wrong...

rogermb commented 9 years ago

Hmm... Have you tried increasing the command timeout via TS3Config.setCommandTimeout(millis)? Might be worth a try.

By default, the timeout is set to 4 seconds, but it could happen that this is not long enough, especially if you're transmitting heaps of data. You maybe try setting it to something like 15 seconds / 15000 ms.

Usually, when a query is disconnected, the API seems to go rouge and starts sending the next keepalive command as soon as the previous one times out, i.e. after 4 seconds.

[2015-09-02 13:31:18.080] [SEVERE] Command whoami was not answered in time.
[2015-09-02 13:31:22.081] [SEVERE] Command whoami was not answered in time.
[2015-09-02 13:31:26.081] [SEVERE] Command whoami was not answered in time.
[2015-09-02 13:31:30.081] [SEVERE] Command whoami was not answered in time.

In your case, this is not what's happening, leading me to believe that maybe it's just occasional commands getting timed out. But I think I'm just as confused as you are ¯_(ツ)_/¯

robingenz commented 9 years ago

Okay ty i will try this. I hope this will work ^^

rogermb commented 9 years ago

I'm going to let my instance run with this code

while (!Thread.interrupted()) {
    long timeToSleep = (long) (Math.random() * TimeUnit.MINUTES.toMillis(15));
    Thread.sleep(timeToSleep);
    api.getClients();
}

until midnight, so for almost 10 hours. If there's an internal problem with the API, I should be able to catch it.

rogermb commented 9 years ago

Almost midnight now, everything's still working as intended.

If your project still doesn't work despite the longer command timeout, I'd have to look through your code to be able to help you further.

robingenz commented 9 years ago

My bot runs now since 5 hours. Tomorrow i'll check how long the bot is running and post the result here.

Kakifrucht commented 9 years ago

Since you are the only one having issues with this I suspect that it has something to do with your teamspeak server / CPU. I run my bot on a digitalocean single core alongside an nginx instance and a teamspeak instance and never had any such problems. The API is as stable as can be.

morrowwolf commented 7 years ago

So I have slight connectivity problems between my computer and teamspeak and generally it doesn't disconnect my client from the server but my bot must have a lower tolerance for dc times since it dies all the time. Is there anyway to increase the tolerance?

rogermb commented 7 years ago 
TS3Config#setCommandTimeout(int milliseconds)

should be what you're looking for. Try increasing it to something like 15000.

If it doesn't just time out but actually disconnects, you could also look into enabling reconnecting (setReconnectStrategy and setConnectionHandler). Example here.

morrowwolf commented 7 years ago

Wow thanks for the extremely quick reply! Will report back if I continue having problems.

morrowwolf commented 7 years ago

[2017-01-09 19:22:15.349] [WARNING] Connection error occurred. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) at sun.nio.cs.StreamDecoder.implRead(Unknown Source) at sun.nio.cs.StreamDecoder.read(Unknown Source) at java.io.InputStreamReader.read(Unknown Source) at java.io.BufferedReader.fill(Unknown Source) at java.io.BufferedReader.readLine(Unknown Source) at java.io.BufferedReader.readLine(Unknown Source) at com.github.theholywaffle.teamspeak3.SocketReader.run(SocketReader.java:72)

[2017-01-09 19:22:15.349] [WARNING] SocketReader has stopped! [2017-01-09 19:22:15.350] [SEVERE] [Connection] Disconnected from TS3 server [2017-01-09 19:22:16.638] [SEVERE] Command quit was not answered in time.

Yeah continues to happen. It just repeats that over and over. I'm not sure if this is the right place to put this problem though. It seems to just happen at random as well since it'll just not be doing anything and die. I used an old version about a year ago and am still running on that code, with the updated API, and it didn't use to do this so I'm unsure what is different that is causing problems.

rogermb commented 7 years ago

That's just plain disconnecting, setting a longer timeout won't fix this.

You'll need to update to a newer version of the API and look into reconnecting :smile:

morrowwolf commented 7 years ago

I'm on the newest API and adapted anything that didn't work any more to the newest version from before. I'm wondering mainly if there's a way to fix this without having to have them reconnect constantly as it's fairly often that they break. Would looking at my code help at all? I don't want to spend too much of your time on my code if it turns out it's an internet problem. The reconnecting solution just feels like a cop out.

rogermb commented 7 years ago

To be honest, it does sound like a simple internet connection problem to me. This should never happen "fairly often" - I've ran this API over several days and never had any disconnects.

If you don't want to go for the reconnecting solution, you could also just run your server query application from the same machine you run your TS3 server on. That would probably be the quickest and cleanest fix.

To be honest, you should do that anyways - there's no guarantee that a command won't get sent a second time after reconnecting, which could always cause subtle problems. Moreover, everything sent over telnet is unencrypted. Everyone with physical access to the packets can simply read out the server query username & password combination.

Both of these problems are caused by one simple thing: Telnet is a bad and utterly broken protocol, and to be frank I have no idea why on earth TeamSpeak would choose such a protocol for a remote management interface. But we can't change it, so we'll just have to live with it.

morrowwolf commented 7 years ago

Yeah I'll give running it on the same machine a try. Thank you for all your time both with helping people and on this project. You're really making people's lives easier as corny as that sounds.

rogermb commented 7 years ago

Thank you for the kind words! I really appreciate it 😊

rogermb commented 6 years ago

Meterpreter? What on earth are you talking about, @fuadhamidli?

This project is a Java wrapper for the TeamSpeak server query interface. It is not in any way affiliated with Metasploit. You're not even targetting any TeamSpeak ports in your screenshot.

And while we're on the topic, why would you leave such a comment on a 2-year-old issue?