• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • A first preview of the unlimited version of SinusBot can be found in the Upcoming Changes thread. A version for Windows will follow, but we don't have a release date, yet.

Solved Bot does not connect

Status
Not open for further replies.

joveice

New Member
Operating System: Windows
SinusBot Version: 0.9.18-8499d2c
TS3 Version: 3.0.19.4

Thanks for deleting my thread, I see how professional this community is.

the server doesn't exist at that address, the server password is wrong: No, the client connects just fine and there are no password.
the default channel doesn't exist: Default channel is 1.
the bot has been banned: Then how can I connect with the same ID?
the server is an illegal installation or the password is wrong: Hosting myself so no, No password.
the security level of your identity is too low or your client version is outdated (the server doesn't allow it anymore): Then the client with the same ID shouldent be able to login.


Problem Description
Bot does not connect.

Code:
2017-04-14T20:58:07+02:00 TSClient quit.
2017-04-14T20:58:07+02:00 Fail from voice reader: EOF
2017-04-14T20:58:07+02:00 Fail from data reader: EOF
2017-04-14T20:58:07+02:00 Closed.
2017-04-14T20:58:06+02:00 New connection status 0; Error 1797
2017-04-14T20:58:06+02: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 your client version is outdated (the server doesn't allow it anymore).
2017-04-14T20:58:01+02:00 New connection status 1; Error 0
2017-04-14T20:57:59+02:00 Starting instance ts3server://192.168.1.2?port=9987&nickname=SinusBot&password=&cid=1&channelpassword=
2017-04-14T20:57:59+02:00 Could not insert into News-Tableno such table: News
2017-04-14T20:57:59+02:00 Could not delete from Newsno such table: News
2017-04-14T20:57:59+02:00 Could not insert into News-Tableno such table: News
2017-04-14T20:57:59+02:00 Could not delete from Newsno such table: News
2017-04-14T20:57:59+02:00 Could not insert into News-Tableno such table: News
2017-04-14T20:57:59+02:00 Could not delete from Newsno such table: News
2017-04-14T20:57:59+02:00 Could not insert into Notifications-Tableno such table: Notifications
2017-04-14T20:57:59+02:00 Could not delete from Notificationsno such table: Notifications
2017-04-14T20:57:59+02:00 Could not insert into Notifications-Tableno such table: Notifications
2017-04-14T20:57:59+02:00 Could not delete from Notificationsno such table: Notifications
2017-04-14T20:57:28+02:00 Initialization complete
 
Last edited:

flyth

is reticulating splines
Staff member
Developer
Contributor
Then the client with the same ID shouldent be able to login.
Usually it's the server not allowing clients < 3.1. I don't get what you mean by ID in that context.

Thanks for deleting my thread, I see how professional this community is.
It says so everywhere. The forum is already cluttered enough with 'doesn't work' posts without any details from people who do not read/honor our simple rules/requests.
 

joveice

New Member
Usually it's the server not allowing clients < 3.1. I don't get what you mean by ID in that context.


It says so everywhere. The forum is already cluttered enough with 'doesn't work' posts without any details from people who do not read/honor our simple rules/requests.
I use the same User ID Token on the Bot as on the teamspeak, and the TS client connects just fine but the bot does not.
 

flyth

is reticulating splines
Staff member
Developer
Contributor
I use the same User ID Token on the Bot as on the teamspeak, and the TS client connects just fine but the bot does not.
That's not a good idea since that might be limited on the server as well. However, that's got nothing to do with the client version which can be different for the bot (and usually is currently). So that's still most likely the reason. There should be documentation on how to configure the server on the forums and / or Wiki.
 

joveice

New Member
That's not a good idea since that might be limited on the server as well. However, that's got nothing to do with the client version which can be different for the bot (and usually is currently). So that's still most likely the reason. There should be documentation on how to configure the server on the forums and / or Wiki.

The server allows 3 clients pr token, and I wasent even logged in at the same time. Got link? I havent found anything to help thats why I went to the forum.
 

karkow

Member
I have the same error as jovice.

I have two servers. Server A and server B (copy of server A)
Sinusbot (from server C) connects to server A normally but with server B receives an error "New connection status 0; Error 1797"
 
Status
Not open for further replies.
Top