• 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.

could not contact update server

AmirHM

Member
1.0.0-beta.10-202ee4d
TS 3.3.2
Ubuntu 16.04 64bit
VPS 8 Core 8G Ram
Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
 - Operating System: Ubuntu 16.04 LTS
 - Kernel: Linux 4.4.0-142-generic x86_64
 - Load Average: 0.85 0.89 0.84
 - Uptime: 22 days, 4 hours, 28 minutes, 41 seconds
 - OS x64 check: OK
 - OS Updates: 13 (updates available!)
 - OS Missing Packages: None
 - OS APT Last Update: 11.02.2020 14:49:59 +0330 +03:30:00
 - Shell Locale: en_US.UTF-8
 - Bot Start Script: not found
 - CPU:
    Architecture:          x86_64
    CPU(s):                8
    Thread(s) per core:    1
    Core(s) per socket:    8
    Socket(s):             1
    CPU MHz:               2500.000
    Hypervisor vendor:     VMware
    Virtualization type:   full
 - RAM: 1.59 GB/7.79 GB in use (20%)
 - SWAP: 31.75 MB/7.99 GB in use (0%)
 - DISK: 28.27 GB/41.21 GB in use (68%)
 - Package versions:
   - libglib: 2.40.2-0ubuntu1.1

BOT INFORMATION
 - Status: not running
 - Webinterface: port locally not reachable (Port: 8087)
 - Binary: /opt/sinusbot/sinusbot
 - Binary Info: MD5 Hash: 224b687db910b732fe5a7cfec4f6c78e, Perms: 755, User: sinusbot
 - Version: 1.0.0-beta.10-202ee4d
 - TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: aa483aea105cb62033392b1ce6d317ab
   - TS3 Client: aa483aea105cb62033392b1ce6d317ab
 - Config:
   - LogLevel = 10
   - TS3Path = /opt/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.3.2)
   - YoutubeDLPath = not set
 - Installed scripts: advertising.js; alonemode.js; bookmark.js; command.js; followme.js; norecording.js; rememberChannel.js; sinusbot-commands.js; welcome.js

BOT TECHNICAL INFORMATION
 - File exists:
   - TS3Client/libqxcb-glx-integration.so: no
 - LDD output:
    linux-vdso.so.1 =>  (0x00007ffe5dd3f000)
    libswresample.so.2 => /opt/sinusbot/libswresample.so.2 (0x00007f08e9b50000)
    libavfilter.so.6 => /opt/sinusbot/libavfilter.so.6 (0x00007f08e97f8000)
    libavformat.so.57 => /opt/sinusbot/libavformat.so.57 (0x00007f08e93f7000)
    libavcodec.so.57 => /opt/sinusbot/libavcodec.so.57 (0x00007f08e8a92000)
    libavutil.so.55 => /opt/sinusbot/libavutil.so.55 (0x00007f08e881e000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f08e861a000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f08e8314000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f08e80f6000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f08e7df2000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f08e7bdc000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f08e7813000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f08e75fa000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f08e73f2000)
    /lib64/ld-linux-x86-64.so.2 (0x00007f08e9d6a000)

REACHABILITY CHECKS
 - HTTPS check with IPv4 mode: SUCCESS [Connection established to www.sinusbot.com, CODE #200]
 - HTTPS check with IPv6 mode: IGNORED [Disabled]
 - DNS resolution check: SUCCESS [www.sinusbot.com resolved to 116.203.111.102]
 - Update server checks:
    update01.sinusbot.com -> 116.203.111.102: SUCCESS [CODE #404]
    update02.sinusbot.com -> 116.203.111.102: SUCCESS [CODE #404]
    update03.sinusbot.com -> 116.203.111.102: SUCCESS [CODE #404]

TIME INFORMATION
 - Time (local): 11.02.2020 15:04:07 +0330 +03:30:00
 - Time (remote): <Failed retrieving remote time!>
 - Time (difference): n/a secs
 - Timezone: Asia/Tehran

OTHER INFORMATION
 - TeamSpeak3 Version: 3.3.2
 - youtube-dl Version: unknown
 - DiagScript Version: 0.8.0
==========================================================
curl -v --no-keepalive --http1.1 https://update01.sinusbot.com output:
Code:
* Rebuilt URL to: https://update01.sinusbot.com/
* Hostname was NOT found in DNS cache
*   Trying 116.203.111.102...
* Connected to update01.sinusbot.com (116.203.111.102) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server key exchange (12):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using ECDHE-ECDSA-AES128-GCM-SHA256
* Server certificate:
*        subject: CN=sni104088.cloudflaressl.com
*        start date: 2020-01-31 00:00:00 GMT
*        expire date: 2020-08-08 23:59:59 GMT
*        subjectAltName: update01.sinusbot.com matched
*        issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO ECC Domain Validation Secure Server CA 2
*        SSL certificate verify ok.
> GET / HTTP/1.1
> User-Agent: curl/7.35.0
> Host: update01.sinusbot.com
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Tue, 11 Feb 2020 11:38:14 GMT
< Content-Type: text/plain
< Content-Length: 0
< Connection: keep-alive
< Set-Cookie: __cfduid=d3abb52df7602ea3dce50e416c97d43a01581421094; expires=Thu, 12-Mar-20 11:38:14 GMT; path=/; domain=.sinusbot.com; HttpOnly; SameSite=Lax
< CF-Cache-Status: DYNAMIC
< Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< Alt-Svc: h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
* Server cloudflare is not blacklisted
< Server: cloudflare
< CF-RAY: 56360910bc8e9bd3-AMS
<
* Connection #0 to host update01.sinusbot.com left intact
dig A +short update01.sinusbot.com output:
Code:
116.203.111.102
 

TwentyFour

BinusSot Junkie
V.I.P.
Contributor
Insider
  • your IP is blacklisted due to suspected non-private use
The most likely cause, as written here.
In case you think there was a mistake or you want to ask for a second chance, post in our forum or discord server and include the following information:
  • your servers IP address
  • output of the curl and dig commands below
Please be polite, explain the situation in detail and provide your IP address!
There is no point in lying, if you are not honest then we are not interested in talking to you.
And since you already posted the outputs, it's time for adding the "missing part". :rolleyes:
 

AliHajipoor

Member
Hello

I have the same problem , my ip address is from the same ISP(158.58.189...) but stillI can't run my sinusbot at all "Could not contact update server"

VPS Location : IRAN

Is there any problem with my ISP ? because i did try run sinusbot with too many ips from that ISP but I failed
 

AliHajipoor

Member
curl -v --no-keepalive --http1.1 https://update01.sinusbot.com output:

Code:
* Rebuilt URL to: https://update01.sinusbot.com/
*   Trying 104.28.15.74...
* TCP_NODELAY set
* Connected to update01.sinusbot.com (104.28.15.74) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Unknown (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Client hello (1):
* TLSv1.3 (OUT), TLS Unknown, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflares                                                                                                             sl.com
*  start date: Feb 12 00:00:00 2020 GMT
*  expire date: Oct  9 12:00:00 2020 GMT
*  subjectAltName: host "update01.sinusbot.com" matched cert's "*.sinusbot.com"
*  issuer: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=CloudFlare Inc E                                                                                                             CC CA-2
*  SSL certificate verify ok.
* TLSv1.3 (OUT), TLS Unknown, Unknown (23):
> GET / HTTP/1.1
> Host: update01.sinusbot.com
> User-Agent: curl/7.58.0
> Accept: */*
>
* TLSv1.3 (IN), TLS Unknown, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS Unknown, Unknown (23):
< HTTP/1.1 404 Not Found
< Date: Wed, 12 Feb 2020 08:17:12 GMT
< Content-Type: text/plain
< Content-Length: 0
< Connection: keep-alive
< Set-Cookie: __cfduid=d7f998c89457315057fa8615b1b526cfc1581495432; expires=Fri,                                                                                                              13-Mar-20 08:17:12 GMT; path=/; domain=.sinusbot.com; HttpOnly; SameSite=Lax
< CF-Cache-Status: DYNAMIC
< Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-c                                                                                                             gi/beacon/expect-ct"
< Alt-Svc: h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
< Server: cloudflare
< CF-RAY: 563d1ff60c721756-FRA
<
* Connection #0 to host update01.sinusbot.com left intact
 

Multivitamin

Well-Known Member
Tier III
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Did you all by any chance started multiple bots or used some malicious installer scripts vom the interwebs which installs multiple sinusbots on different ports?
 

AliHajipoor

Member
Hi, no those ips I did try to start sinusbot are new generated by my datacenter And before that there was no bot running on it
 

AmirHM

Member
Did you all by any chance started multiple bots or used some malicious installer scripts vom the interwebs which installs multiple sinusbots on different ports?
No
I tested installing sinusbot on windows with the same IP it worked fine but in linux it didn't work
 
Top