• If you need help or want to discuss things, you now can also join us on our Discord Server!

Solved Bot can't join - Bot kann nicht joinen

#1
English:
Hey, I just installed Sinusbot, and the bot can't join my server. Has anybody got an idea? I already tried my own Identity and the one given by Sinusbot.
Here is the instance log part:
Code:
2018-11-17T22:03:17+01:00 Starting instance ts3server:///********.de?port=9987&nickname=**************&password=&channel=&channelpassword=
2018-11-17T22:03:17+01:00 Could not create Notifications-Tabletable Notifications already exists
2018-11-17T22:03:17+01:00 Could not create WhisperReceive-Tabletable WhisperReceive already exists
2018-11-17T22:03:17+01:00 Could not create Chat-Tabletable Chat already exists
2018-11-17T22:03:15+01:00 TSClient quit.
2018-11-17T22:03:14+01:00 TS |INFO | | |Statistics report: Not yet, next report on Wed Dec 5 21:58:03 2018
2018-11-17T22:03:14+01:00 TS |INFO |ClientUI | |Last update check was: Tue Jan 1 00:00:01 2019
2018-11-17T22:03:14+01:00 TS |INFO |Bookmarks | |Collecting autoconnect bookmarks
2018-11-17T22:03:14+01:00 New connection status 0; Error 1037
2018-11-17T22:03:14+01:00 The bot could not connect. This might have several reasons: the server doesn't exist at that address, the server password is wrong, the default channel doesn't exist, the bot has been banned, the server is an illegal installation or the password is wrong , the security level of your identity is too low or the server does not allow the version of the client you are using. See our Wiki / Forums for more help.
Deutsch:
Hey, ich habe gerade Sinusbot installiert, und der Bot kann meinen Server nicht joinen. Hat jemand eine Idee? Ich habe auch bereits eine eigene Identität und die vorgegebene probiert.
Hier ist der Instance Log Abschnitt:
Code:
2018-11-17T22:03:17+01:00 Starting instance ts3server:///********.de?port=9987&nickname=**************&password=&channel=&channelpassword=
2018-11-17T22:03:17+01:00 Could not create Notifications-Tabletable Notifications already exists
2018-11-17T22:03:17+01:00 Could not create WhisperReceive-Tabletable WhisperReceive already exists
2018-11-17T22:03:17+01:00 Could not create Chat-Tabletable Chat already exists
2018-11-17T22:03:15+01:00 TSClient quit.
2018-11-17T22:03:14+01:00 TS |INFO | | |Statistics report: Not yet, next report on Wed Dec 5 21:58:03 2018
2018-11-17T22:03:14+01:00 TS |INFO |ClientUI | |Last update check was: Tue Jan 1 00:00:01 2019
2018-11-17T22:03:14+01:00 TS |INFO |Bookmarks | |Collecting autoconnect bookmarks
2018-11-17T22:03:14+01:00 New connection status 0; Error 1037
2018-11-17T22:03:14+01:00 The bot could not connect. This might have several reasons: the server doesn't exist at that address, the server password is wrong, the default channel doesn't exist, the bot has been banned, the server is an illegal installation or the password is wrong , the security level of your identity is too low or the server does not allow the version of the client you are using. See our Wiki / Forums for more help.
 

Kir-à

Helping Hand
is awesome!
Contributor
#2
we've literally zero info with this instance logs.

Check if theses informations are filled:

The bot could not connect. This might have several reasons: the server doesn't exist at that address, the server password is wrong, the default channel doesn't exist, the bot has been banned, the server is an illegal installation or the password is wrong , the security level of your identity is too low or the server does not allow the version of the client you are using. See our Wiki / Forums for more help.

 
#3
I fixed it. I got told that the Teamspeak Server updates itself automatically, but it didn't. It was on 3.1.something. It is working now.
 

Similar threads