David1981
Active Member
Good evening i have a problem. Server security level i have to 8 . And for some reason, bots still can't connect to the ts3 server. I tried everything, created my own identity for each corvee. The password in the channel is not that it can connect .License The version of ts3 is legal and lilcence corvee. The ts3 version is 3.13.1 Linux. I still thought of the sinusbot version fines there is no problem push. Here I present what he writes: Instance-LOG. How to make it so that the shoes don't fall .I'll load the plugin there and crash all corvee. Thank you very much everyone for the advice I appreciate it . Dave
2020-11-20T01:05:25+01:00 TS |INFO |TSDNS | |No TSDNS found
2020-11-20T01:05:25+01:00 TS |INFO |TSDNS | |TSDNS queried unsuccessfully 89.221.219.208:41144
2020-11-20T01:05:23+01:00 New connection status 1; Error 0
2020-11-20T00:42:46+01:00 Storing configuration.
2020-11-20T00:42:21+01:00 closing channels
2020-11-20T00:42:20+01:00 TSClient quit. LogLevel has been increased, please try to connect again to see more details.
2020-11-20T00:42:19+01:00 TS |INFO | | |Statistics report: User has not yet confirmed participation
2020-11-20T00:42:19+01:00 TS |INFO |ClientUI | |Last update check was: Sat Jan 1 00:00:01 2022
2020-11-20T00:42:19+01:00 TS |INFO |Bookmarks | |Collecting autoconnect bookmarks
2020-11-20T00:42:19+01:00 New connection status 0; Error 0
2020-11-20T00:42:19+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, the password is wrong, the security level of your identity is too low, the nickname is too short or too long or the server does not allow the version of the client you are using. See our Wiki / Forums for more help.
2020-11-20T01:05:25+01:00 TS |INFO |TSDNS | |No TSDNS found
2020-11-20T01:05:25+01:00 TS |INFO |TSDNS | |TSDNS queried unsuccessfully 89.221.219.208:41144
2020-11-20T01:05:23+01:00 New connection status 1; Error 0
2020-11-20T00:42:46+01:00 Storing configuration.
2020-11-20T00:42:21+01:00 closing channels
2020-11-20T00:42:20+01:00 TSClient quit. LogLevel has been increased, please try to connect again to see more details.
2020-11-20T00:42:19+01:00 TS |INFO | | |Statistics report: User has not yet confirmed participation
2020-11-20T00:42:19+01:00 TS |INFO |ClientUI | |Last update check was: Sat Jan 1 00:00:01 2022
2020-11-20T00:42:19+01:00 TS |INFO |Bookmarks | |Collecting autoconnect bookmarks
2020-11-20T00:42:19+01:00 New connection status 0; Error 0
2020-11-20T00:42:19+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, the password is wrong, the security level of your identity is too low, the nickname is too short or too long or the server does not allow the version of the client you are using. See our Wiki / Forums for more help.
Last edited: