The bot could not connect.

[micro_maniaque]

Hello,

Sinusbot already using for several months I have to buy a small VPS sinusbot only. The VPS is a debian August 64 bits with 2 GB of DDR3 and 2 virtual cores.

When I run the bot panel is available but can not connect to the TeamSpeak VPS but with our second problem.

Here are some of the logs:

2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Lookup finished: 151.80.47.219 9987 ts.badblock.fr 0 0
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Resolve successful: 151.80.47.219:9987
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Blacklist check ok
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Initiating connection: 151.80.47.219:9987 ts.badblock.fr
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |PreProSpeex   |1  |Speex version: 1.2rc1
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Connect status: Connecting
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   New connection status 1; Error 0
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |   |Last update check was: dim. janv. 1 00:00:01 2017
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |   |Checking for update
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |Update        |   |Checking for updates...
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |Update        |   |Check license version: 1
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |LicenseViewer |   |License language: en
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |LicenseViewer |   |Requesting remote license for version 1 and language en
2015/12/31 23:14:42 657dd36c ebbfd2a5 INFO   TS |INFO    |LicenseViewer |   |Downloaded license file for version 1 and language en
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |INFO    |Newsticker    |   |Newsticker language change detected
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |INFO    |Newsticker    |   |Newsticker next check:
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |DEVELOP |PktHandler    |   |Puzzle solve time: 4
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |INFO    |Newsticker    |   |Newsticker received for language en, expires on jeu. déc. 31 23:44:43 2015, next check in 1800 seconds
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Connect status: Disconnected
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   TS |INFO    |ClientUI      |1  |Disconnected or forced to leave, want autoreconnect = 0
2015/12/31 23:14:43 657dd36c ebbfd2a5 INFO   The bot could not connect. This might have several reasons: the server doesn't exist at that address, the server password is wrong or the security level of your identity is too low.
2015/12/31 23:14:48 657dd36c ebbfd2a5 WARN   Could not request shutdown. Please make sure that the loopback interface is not firewalled.
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   New connection status 0; Error 0
2015/12/31 23:14:49 657dd36c ebbfd2a5 WARN   Could not find request%!(EXTRA uint32=5)
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   TS>libpng warning: iCCP: known incorrect sRGB profile
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   TS>warning: The VAD has been replaced by a hack pending a complete rewrite
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   TS>qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   TS>qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method
2015/12/31 23:14:49 657dd36c ebbfd2a5 INFO   TSClient quit.
2015/12/31 23:14:49 X [MAIN] Disconnected:  6
2015/12/31 23:14:49 X [MAIN] Disconnected:  5
2015/12/31 23:14:54 657dd36c ebbfd2a5 WARN   Could not send config. Please make sure that the loopback interface is not firewalled and the plugin is installed properly.
2015/12/31 23:14:54 657dd36c ebbfd2a5 WARN   Could not send config. Please make sure that the loopback interface is not firewalled and the plugin is installed properly.

Here's a screenshot:

Thank you for helping me solve this problem that bothers me a little. I also informed him that I have this concern since the last update of SinusBot. Before I never had this trouble.

Best regards
micro_maniaque