Deprecated: Use of "parent" in callables is deprecated in /var/www/html/forum/src/vendor/league/flysystem-eventable-filesystem/src/EventableFilesystem.php on line 431
  • 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 [Emergency]

AliHajipoor

Member
Hello guys, recently I bought a VPS from Asia Tech ISP (Location : IRAN) , and when I want to start my sinusbot (beta) the error shows up "Could not contact update server"

My ip was generate recently and before thatt here was no bot running on it I thought the ip that I recieved is block from sinusbot by after I did try with another ip from the same range IP but the problem didn't solve, Attention : Its only one sinusbot, not multiple ports. and my timezone is up to date.

My IP : 158.58.189.164 , 158.58.189.163

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

Code:
*   Trying 104.28.14.74:443...
* TCP_NODELAY set
* Connected to update01.sinusbot.com (104.28.14.74) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.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 ECC CA-2
*  SSL certificate verify ok.
> GET / HTTP/1.1
> Host: update01.sinusbot.com
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< Date: Wed, 12 Feb 2020 19:08:41 GMT
< Content-Type: text/plain
< Content-Length: 0
< Connection: keep-alive
< Set-Cookie: __cfduid=d875b47ac76251c16d2d7e4d43076dabc1581534521; expires=Fri, 13-Mar-20 19:08:41 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
< CF-RAY: 5640da482f1bd6ed-FRA
<
* Connection #0 to host update01.sinusbot.com left intact

dig A +short update01.sinusbot.com output:
Code:
104.28.14.74
104.28.15.74
 
Top