TeamSpeak Server prematurely closed the connection
vedrandev opened this issue · comments
Hello, when i try to connect to my teamspeak server i get this error. Can you help me ?
(node:8451) UnhandledPromiseRejectionWarning: Error: TeamSpeak Server prematurely closed the connection at TeamSpeak.closeCallback (/root/teamspeak bots/node_modules/ts3-nodejs-library/lib/TeamSpeak.js:130:24) at Object.onceWrapper (events.js:421:26) at TeamSpeak.emit (events.js:314:20) at TeamSpeakQuery.<anonymous> (/root/teamspeak bots/node_modules/ts3-nodejs-library/lib/TeamSpeak.js:58:45) at TeamSpeakQuery.emit (events.js:314:20) at TeamSpeakQuery.handleClose (/root/teamspeak bots/node_modules/ts3-nodejs-library/lib/transport/TeamSpeakQuery.js:205:14) at ProtocolRAW.emit (events.js:314:20) at ProtocolRAW.handleClose (/root/teamspeak bots/node_modules/ts3-nodejs-library/lib/transport/protocols/raw.js:47:14) at Socket.emit (events.js:314:20) at TCP.<anonymous> (net.js:675:12) (node:8451) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:8451) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
This happens because the Server doesnt send any Welcome Message but closes the connection instantly
probably you mistakenly connect to the wrong port, maybe you are banned from the server and need to wait 10 minutes before reconnecting (might be due to wrong entered password)
First time I connected successful but when I try to connect again I get this error, I am not banned or something like that
try connect manually with SSH or Telnet and see if it happens there, be sure that you have the correct ip address while doing that
I fixed it with restarting my server