Closed rickjames1337 closed 1 year ago
Please try without proxies, i.e. empty proxy_list.txt
Ah yeah it worked probably just bad proxies then?
Another user reported he had to refresh the proxies in the webshare.io dashboard.
Issue still happens even after refreshing. It works fine for a hot minute then dies out again. I know I can only refresh my proxies 9 times a month so not feasible to do it everytime it dies so I just stopped using the program.
Can you check for errors in the dashboard under Stats -> Error?
target_read_idle_timeout
This issue is new to me. I will try on my side. Does anyone have the same problem?
This issue is new to me. I will try on my side. Does anyone have the same problem?
hello man, yes, i have the same issue with the linux application too. I can share the logs if you need. thank you.
Please do or send me via mail.
Please do or send me via mail.
sent, thank you.
ToDo:
I added the feature that each connection is tried three times. This could mitigate the problem, but only if the problem lies with CTVBot. Please download the latest version: https://github.com/jlplenio/crude-twitch-viewer-bot/releases/latest
ill try now, return soon with feedback :D
I'm still having some problems, I'll report them below.
OS: Linux Version: 0.5.3 Ubuntu Linux VPS with XRDP Proxy: WebShare.io Running for more than 13h
CTVBot is not opening more than 20 instances, when reaching the 20th instance it seems to give timeOut and only opens new ones, when old ones are closed. This version seems to be less unstable than the previous one (0.5.2)
When leaving 20 instances active, after 13 hours running it closed all instances and did not reopen them (restart with failure).
CTVBot is having trouble opening and most of the time it gives Timeout.
CTVBot is closing repeatedly, after some open instances, it closes completely and it is necessary to open everything again.
log is attached ctvbot.log, substitute my login part for XXXXX to hide this information as the LOG is here on github.
Hmmm I cannot recreate it. I tried for an hour with stable cpu, ram, traffic and 100 viewers at 160p.
Maybe your VPS provider is reducing your bandwidth if you generate too much traffic?
Do a barrel roll ehm speedtest.
@ricardopereirasilveira 13h was online your stream ? I think to resolve this problem, is required to start and stop instances using API based if stream is online or offline. PS. I know @jlplenio don't want this to prevent commercialization of bot
Reopen if the problem reoccurs.