Possible blacklist? "a manual update is required"

[kanalumaddela]

Been a while since I've made a thread, haven't been active here, but still actively had the bot running (on a license) for my community until recently where it wouldn't start.
None of the latest versions, both internal and public for linux work for me, even as a fresh setup.

Server time seems to be in sync, so I don't think that's the issue, but who knows.

My VPS IP did change "recently" (sometime in the previous months) from 192.223.26.175 -> 74.91.119.170, so I'm assuming maybe it's being blacklisted?

• curl -v --no-keepalive --http1.1 https://update01.sinusbot.com returns a 403 with CF's captcha page
• Host is NFOservers

diagSinusbot.sh output

==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
 - Operating System: Debian GNU/Linux 9.13 (stretch)
 - Kernel: Linux 4.9.0-12-amd64 x86_64
 - Load Average: 0.03 0.10 0.16
 - Uptime: 0 days, 15 hours, 52 minutes, 35 seconds
 - OS x64 check: OK
 - OS Updates: 0 (well done!)
 - OS Missing Packages: None
 - OS APT Last Update: 02.08.2020 15:31:22 CDT -05:00:00
 - Shell Locale: en_US.UTF-8
 - Bot Start Script: found at /etc/init.d/sinusbot [perms: 755]
 - CPU:
    Architecture:          x86_64
    CPU(s):                4
    Thread(s) per core:    1
    Core(s) per socket:    4
    Socket(s):             1
    Model name:            Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
    CPU MHz:               3000.166
    Hypervisor vendor:     Xen
    Virtualization type:   full
 - RAM: 2.17 GB/3.85 GB in use (56%)
 - SWAP: 0 B/0 B in use (0%) (SWAP disabled)
 - DISK: 122.71 GB/590.58 GB in use (20%)
 - Package versions:
   - libglib: 2.50.3-2+deb9u2

BOT INFORMATION
 - Status: not running
 - Webinterface: port locally not reachable (Port: 8088)
 - Binary: /home/sinusbot/ts3bots/sinusbot-test/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 = 3
   - TS3Path = /home/sinusbot/ts3bots/sinusbot-test/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.5.3)
   - YoutubeDLPath = not set (does exist anyway, version: 2020.07.28)
 - 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: yes
 - LDD output:
    linux-vdso.so.1 (0x00007fff3db83000)
    libswresample.so.2 => /home/sinusbot/ts3bots/sinusbot-test/libswresample.so.2 (0x00007fcaffa7e000)
    libavfilter.so.6 => /home/sinusbot/ts3bots/sinusbot-test/libavfilter.so.6 (0x00007fcaff726000)
    libavformat.so.57 => /home/sinusbot/ts3bots/sinusbot-test/libavformat.so.57 (0x00007fcaff325000)
    libavcodec.so.57 => /home/sinusbot/ts3bots/sinusbot-test/libavcodec.so.57 (0x00007fcafe9c0000)
    libavutil.so.55 => /home/sinusbot/ts3bots/sinusbot-test/libavutil.so.55 (0x00007fcafe74c000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fcafe548000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fcafe244000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fcafe027000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fcafdca5000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fcafda8e000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcafd6ef000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fcafd4d5000)
    librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fcafd2cd000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fcaffc98000)

REACHABILITY CHECKS
 - HTTPS check with IPv4 mode: FAILED [Failed connection to www.sinusbot.com, CODE #403]
 - HTTPS check with IPv6 mode: IGNORED [Disabled]
 - DNS resolution check: SUCCESS [www.sinusbot.com resolved to 172.67.132.160]
 - Update server checks:
    update01.sinusbot.com -> 104.28.15.74: FAILED [CODE #403]
    update02.sinusbot.com -> 104.28.15.74: FAILED [CODE #403]
    update03.sinusbot.com -> 172.67.132.160: FAILED [CODE #403]

TIME INFORMATION
 - Time (local): 02.08.2020 15:53:36 CDT -05:00:00
 - Time (remote): 02.08.2020 15:53:36 CDT -05:00:00
 - Time (difference): 0 secs (Time diff less than 2 secs. Good.)
 - Timezone: America/Chicago

OTHER INFORMATION
 - TeamSpeak3 Version: 3.5.3
 - youtube-dl Version: 2020.07.28
 - DiagScript Version: 0.8.0
==========================================================

 

[Multivitamin]

seems like cloudflare is blocking the connection to the update servers
if you have any gui or vpn install to connect via the servers ip to https://update01.sinubot.com you can solve the captcha from cloudflare there and you should be fine again

 

[kanalumaddela]

seems like cloudflare is blocking the connection to the update servers
if you have any gui or vpn install to connect via the servers ip to https://update01.sinubot.com you can solve the captcha from cloudflare there and you should be fine again

CF adds a cookie once you get past their captcha, so in command line, this won't work, even if I were to send a test request with the cookies curl -b 'cookie=value' and it wouldn't make sense to control how the bot sends requests upon start up.

I had setup a test bot on my home computer and it worked without issues, so I'll either have to use a different host or just run it off my home computer :/.

As a side note: maybe mention in the installation FAQ for What does "a manual update is required" mean? that it's also possible that the user's IP is blacklisted and is triggering CF because there was never an error related to being unable to contact the update server even though that was the literal reason behind this.