Not-Connect in TeamSpeak3

[Filipe Lopes]

SinusBot Version: 0.12
TeamSpeak3: 3.1.7
System: Debian 8
VPS: OMGServ



So I bought a teamspeak3 in Brazil and Bot does not connect to it saying the error
"2018-02-07T22: 11: 38-02: 00 TSClient quit. "
"2018-02-07T22: 11: 37-02: 00 New connection status 0; Error 1797 "
"2018-02-07T22: 11: 37-02: 00 The bot could not connect. This may have several reasons: the server does not exist at that address, the server password is wrong, the default channel does not 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. "

How do I solve this?

 

[flyth]

The bot could not connect. This may have several reasons: the server does not exist at that address, the server password is wrong, the default channel does not 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.

As usual by fixing all of those, using the diag script etc. Come on, you're not new here

 

[Filipe Lopes]

[QUOTE = "flyth, post: 26822, member: 2"] Como de costume, corrigindo todos esses, usando o script diag, etc. Venha, você não é novo aqui [/ QUOTE]

Is it for me to use the diagnosis?

 

[Filipe Lopes]

As usual by fixing all of those, using the diag script etc. Come on, you're not new here

[2018-02-10 13:38:43] [ERROR] Failed trieving remote time from NTP server time.google.com! Is any firewall blocking the NTP request, or is the DNS resolution failing?

Results:

==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Debian GNU/Linux 8.10 (jessie) (OpenVZ)
- Kernel: Linux 2.6.32-openvz-042stab127.2-amd64 x86_64
- Load Average: 1.54 1.69 1.70
- Uptime: 6 days, 18 hours, 2 minutes, 46 seconds
- OS x64 check: OK
- OS Updates: 5 (updates available!)
- OS Missing Packages: None
- OS APT Last Update: 10.02.2018 04:30:30 CET +01:00:00
- SHELL LOCALE LANG: en_US.UTF-8
- Bot Start Script: not found
- DNS resolution check: www.sinusbot.com resolved to CENSURED -> OK
- HTTPS check with IPv4 mode: SUCCESS [Connection was established to www.sinusbot.com, CODE #200]
- HTTPS check with IPv6 mode: IGNORE
- CPU:
    (failed retrieving information)
- RAM:  B/8.00 GB in use (%)
- SWAP:  B/ B in use (%)
- DISK: 5.38 GB/31.86 GB in use (16%)
- Package versions:
   + libglib: 2.42.1-1+b1

BOT INFORMATION
- Status: running (PIDs: 27974 27973, User: sinusbot)
- Webinterface: port locally reachable (Port: 8087)
- Binary: /opt/sinusbot/sinusbot
- Binary Info: MD5 Hash: b097bbf0f81f38b8c10ef60ee0091d94, Perms: 755, User: root
- Version: 0.12.0-9057353
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: d97c77abca35d95e832bb86aff385f5a
   - TS3 Client: d97c77abca35d95e832bb86aff385f5a
- Config:
   - LogLevel = 3
   - TS3Path = /opt/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.1.7)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2018.01.21)
- Installed scripts: advertising.js; alonemode.js; bookmark.js; followme.js; Minecraft_Server_Info.js; norecording.js; rememberChannel.js; welcome.js; YT-search.js

TIME INFORMATION
- Time (local): 10.02.2018 13:38:43 CET +01:00:00
- Time (remote): <Failed retrieving remote time!>
- Time (difference): n/a secs
- Timezone: Europe/Paris

OTHER INFORMATION
- TeamSpeak 3 Version: 3.1.7
- youtube-dl Version: 2018.01.21
- DiagScript Version: 0.7.0
==========================================================

 

[Filipe Lopes]

The only bug in the Diagnostics was the one above and here shows me trying to connect the bot after using the diagnosis.

 

[flyth]

Your bot can't reach your server as it seems or you server's IP has been banned. Can't help you more than that.

 

[Filipe Lopes]

Your bot can't reach your server as it seems or you server's IP has been banned. Can't help you more than that.

I checked here and the ban list has no ban and my friend has a vps on the same host as mine and his bots can connect, I checked in here in the community had a topic of a guy with the same error and the guy gave up try to solve the problem :/

 

[Filipe Lopes]

:/, help?