xDefcon / sinusbot-scripts

Scripts for SinusBot (sinusbot.com)
GNU General Public License v3.0
14 stars 10 forks source link

Bot Detects permanently Clients as Proxy #25

Closed klopek99 closed 6 years ago

klopek99 commented 6 years ago

I updateted to Version 2.0 a few Minutes ago. The Bot escalated and Checked all Clients from the Server. He says permanently that everyone has an Proxy and Spams the Message. Without activating the Antibypass the Bot detects everyone as a bypasser.After that i activated it and deactivated, trying to stop the Antibypass but it keeps checking people. The Bot has enough Permissions, but cant retrieve the IP Adresses from Clients, thats why he dont write the IP into the Detected Proxy Message. Additionally he isn`t able to read the "Total Client Connections" and the "First connection" and says on every Client he has 0 Total Connections and the first connection was at 31 Dec 1969.

xDefcon commented 6 years ago

Wow, this seems strange to me.

Can you ensure the bot has the correct permissions? Enable debug in the config and attach a log file here, I'll check better.

Thanks.

klopek99 commented 6 years ago

Yes, i'm sure the bot has correct permissions he's already running over a few months without problems on the old Version. Here is the Link with the Debug messages: https://pastebin.com/removed I felt free and made a Video how it looks like in the Chat: https://youtu.be/removed It's not speed upped, It's realtime.

xDefcon commented 6 years ago

Ouch, that is definitely a bug, now the problem is replicating it. Can you send a pic of the current AntiProxy configuration in the web interface? Thanks.

xDefcon commented 6 years ago

@klopek99 bump 👍

IMmmKI commented 6 years ago

Do you guys mind removing the pastebin link as it has client IPs, etc. :)

xDefcon commented 6 years ago

Do you guys mind removing the pastebin link as it has client IPs, etc. :)

Totally true, removed links

IMmmKI commented 6 years ago

I am seeing the same error. Here is the screen of the settings.

image

image

xDefcon commented 6 years ago

2.1 should solve this problem, be sure to run the latest SinusBot version in combination with AntiProxy 2.1 (reopen the issue for further problems)