Hello, currently it's not possible to correctly manage TeaSpeak Server instances correctly with EasyWI (a very popular and modern opensource game and voice administration interface), because of TeaSpeaks api handling and EasyWIs way of responding to it.
This appears upon server creation:
Somehow trying to change the amount of slots a server has, results in even more errors:
Ok then, trying to start the virtual server we created?
Trying to read and change server settings from the client side, reading the settings from the instance won't get any results at all, but saving seems to change some settings on the server:
Ok just forget that unimportant stuff, let's just make an Token from the user interface for me to become an admin and start doing stuff!
Well... No. Can't select any group because of faulty response. Ok then let's create an token for no group.
EasyWI reports:
"TS3 Serverquery fehlerhaft. Manipulation entdeckt!"
TS3 serverquery faulty. Manipulation found!
It seems like the reponses that the api gives, aren't completely compatible with the ones from Tea*Speak.
And yes, I get that this won't be Tea*Speak! And we hope that it becomes something way better.
But in order to spread it more widely, you have to make the entry point lower and provide anyone a solution they can work with already existing interfaces, control panels and software.
Wasn't TeaSpeaks slogan something like "Because a license fee is not my cup of tea!"? Why forcing users to pay additional licensing fees for Tea*Speak-interface.de then? I don't see, where the costs saved are adding up here and how this is user and provider friendly when you have to put so much effort in rewriting code, you sometimes even can't change yourself, because it is closed source?
The way the api works right now mostly or partially isn't compatible with some great pieces of software right now, what makes managing it somehow a pain in the ***.
Here's a list, because it's written so, I heard of or tested quite a few of them:
Software I know of that you can't get to work with right now:
Software that mostly works but throws error messages every now and then:
Software that seems to be working perfectly fine:
This appears upon server creation:
Code:
[2018-09-15 21:37:14] [INFO] QUERY | Got new client from x:41086
[2018-09-15 21:37:15] [INFO] 2 | Got 0 saved channels
[2018-09-15 21:37:15] [INFO] 2 | Creating new channel tree (Copy from server 0)
[2018-09-15 21:37:15] [INFO] 2 | Got 4 saved channels
[2018-09-15 21:37:16] [INFO] 2 | ---------------------- Token ----------------------
[2018-09-15 21:37:16] [INFO] 2 | The server's serveradmin token:
[2018-09-15 21:37:16] [INFO] 2 | x
[2018-09-15 21:37:16] [INFO] 2 |
[2018-09-15 21:37:16] [INFO] 2 | Note: This token could be used just once!
[2018-09-15 21:37:16] [INFO] 2 | ---------------------- Token ----------------------
[2018-09-15 21:37:16] [ERROR] 2 | Failed to bind to 0.0.0.0:9987 (98 => Address already in use)
[2018-09-15 21:37:16] [ERROR] 2 | Failed to bind to :::9987 (98 => Address already in use)
[2018-09-15 21:37:16] [ERROR] GLOBL | Could not stop server tick task!
[2018-09-15 21:37:16] [ERROR] GEN | Command handling of command servercreate needs 108ms
[2018-09-15 21:37:16] [ERROR] QUERY | [x:41086/Easy-WI] Failed to read! Code: -1 errno: 104 message: Connection reset by peer
[2018-09-15 21:37:16] [INFO] GEN | [Query] 173.249.55.96:41086 disconnected. (Requested by manager)
[2018-09-15 21:37:16] [ERROR] QUERY | [x:41086/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:37:16] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:37:16] [ERROR] QUERY | Tried to disconnect a client twice!
Code:
[2018-09-15 21:38:32] [INFO] QUERY | Got new client from x:41120
[2018-09-15 21:38:32] [ERROR] QUERY | [x:41120/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:38:32] [ERROR] QUERY | [x:41120/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:32] [ERROR] QUERY | [x:41120/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:32] [INFO] GEN | [Query] x:41120 disconnected. (Requested by manager)
[2018-09-15 21:38:32] [ERROR] QUERY | [x:41120/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:32] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:38:32] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:38:53] [INFO] QUERY | Got new client from x:41126
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [ERROR] QUERY | [x:41126/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:54] [INFO] GEN | [Query] x:41126 disconnected. (Requested by manager)
[2018-09-15 21:38:54] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:38:54] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:38:58] [INFO] QUERY | Got new client from x:41132
[2018-09-15 21:38:58] [ERROR] QUERY | [x:41132/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:38:58] [ERROR] QUERY | [x:41132/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:58] [ERROR] QUERY | [x:41132/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:58] [ERROR] QUERY | [x:41132/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:58] [INFO] GEN | [Query] x:41132 disconnected. (Requested by manager)
[2018-09-15 21:38:58] [ERROR] QUERY | [x:41132/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:38:58] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:38:58] [ERROR] QUERY | Tried to disconnect a client twice!
Ok then, trying to start the virtual server we created?
Code:
[2018-09-15 21:40:01] [INFO] QUERY | Got new client from x:41146
[2018-09-15 21:40:02] [ERROR] QUERY | [173.249.55.96:41146/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:40:02] [INFO] GEN | [Query] x:41146 disconnected. (Requested by manager)
[2018-09-15 21:40:02] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:40:58] [INFO] QUERY | Got new client from x:41162
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] 2 | Failed to bind to 0.0.0.0:9987 (98 => Address already in use)
[2018-09-15 21:40:58] [ERROR] 2 | Failed to bind to :::9987 (98 => Address already in use)
[2018-09-15 21:40:58] [ERROR] GLOBL | Could not stop server tick task!
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [ERROR] QUERY | [x:41162/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:40:58] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
Trying to read and change server settings from the client side, reading the settings from the instance won't get any results at all, but saving seems to change some settings on the server:
Code:
[2018-09-15 21:43:11] [INFO] QUERY | Got new client from x:41202
[2018-09-15 21:43:12] [ERROR] QUERY | [x:41202/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:43:12] [ERROR] QUERY | [x:41202/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:12] [ERROR] QUERY | [x:41202/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:12] [ERROR] QUERY | [x:41202/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:12] [INFO] GEN | [Query] x:41202 disconnected. (Requested by manager)
[2018-09-15 21:43:12] [ERROR] QUERY | [x:41202/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:12] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:43:12] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:43:32] [INFO] QUERY | Got new client from x:41214
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [INFO] GEN | [Query] x:41214 disconnected. (Requested by manager)
[2018-09-15 21:43:32] [ERROR] QUERY | [x:41214/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:32] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:43:32] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:43:36] [INFO] QUERY | Got new client from x:41218
[2018-09-15 21:43:36] [ERROR] QUERY | [x:41218/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:43:36] [ERROR] QUERY | [x:41218/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:36] [ERROR] QUERY | [x:41218/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:36] [INFO] GEN | [Query] x:41218 disconnected. (Requested by manager)
[2018-09-15 21:43:36] [ERROR] QUERY | [x:41218/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:43:36] [CRITICAL] QUERY | Could not shutdown query client socket
Well... No. Can't select any group because of faulty response. Ok then let's create an token for no group.
Code:
[2018-09-15 21:46:28] [INFO] QUERY | Got new client from x:41258
[2018-09-15 21:46:29] [ERROR] QUERY | [x:41258/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:46:29] [INFO] GEN | [Query] x:41258 disconnected. (Requested by manager)
[2018-09-15 21:46:29] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:46:33] [INFO] QUERY | Got new client from x:41266
[2018-09-15 21:46:34] [ERROR] QUERY | [x:41266/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:46:34] [ERROR] QUERY | [x:41266/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:46:34] [ERROR] QUERY | [x:41266/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:46:34] [ERROR] QUERY | [x:41266/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:46:34] [INFO] GEN | [Query] x:41266 disconnected. (Requested by manager)
[2018-09-15 21:46:34] [ERROR] QUERY | [x:41266/Easy-WI] Failed to write message: -1 (32 => Broken pipe)
[2018-09-15 21:46:34] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:46:34] [ERROR] QUERY | Tried to disconnect a client twice!
[2018-09-15 21:46:38] [INFO] QUERY | Got new client from x:41270
[2018-09-15 21:46:39] [ERROR] QUERY | [x:41270/serveradmin] Failed to read! Code: 0 errno: 32 message: Broken pipe
[2018-09-15 21:46:39] [INFO] GEN | [Query] x:41270 disconnected. (Requested by manager)
[2018-09-15 21:46:39] [CRITICAL] QUERY | Could not shutdown query client socket! 107 (Transport endpoint is not connected)
[2018-09-15 21:46:39] [ERROR] QUERY | Tried to disconnect a client twice!
"TS3 Serverquery fehlerhaft. Manipulation entdeckt!"
TS3 serverquery faulty. Manipulation found!
It seems like the reponses that the api gives, aren't completely compatible with the ones from Tea*Speak.
And yes, I get that this won't be Tea*Speak! And we hope that it becomes something way better.
But in order to spread it more widely, you have to make the entry point lower and provide anyone a solution they can work with already existing interfaces, control panels and software.
Wasn't TeaSpeaks slogan something like "Because a license fee is not my cup of tea!"? Why forcing users to pay additional licensing fees for Tea*Speak-interface.de then? I don't see, where the costs saved are adding up here and how this is user and provider friendly when you have to put so much effort in rewriting code, you sometimes even can't change yourself, because it is closed source?
The way the api works right now mostly or partially isn't compatible with some great pieces of software right now, what makes managing it somehow a pain in the ***.
Here's a list, because it's written so, I heard of or tested quite a few of them:
Software I know of that you can't get to work with right now:
Tea*Speak Interface by Psychokiller(reported to be working)- TekBase (not verified)($$$)
- EasyWI
tsviewer.com(works now, some users in this forum complained it didn't in the past)Tea*Speak 3 PHP Framework(works in newer versions)
Software that mostly works but throws error messages every now and then:
- YaTQa
Software that seems to be working perfectly fine:
- Tea*Speak-interface.de ($$$)
- WHMCS Tea*Speak ($$$)
- Tea*Speak 3 PHP Framework
- tsviewer.com
- Tea*Speak Interface by Psychokiller
Last edited: