-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread failed to connect #124
Comments
That's really strange, I'm not sure what would cause that, looks like something unusual about your environment. Is your traffic going through any proxies or fancy firewalls that might be doing traffic shaping or suchlike? Also, assuming you're currently running Burp via the jar, can you try using the installer version? This will put you on the same JRE as most users. |
I also thought that maybe was an issue with my VPN but turning it off didn't change anything |
That's a crazy low RPS. Are you seeing that regardless of the target domain? Maybe you've got an anti-virus that's doing some horrific local MITM stuff? |
Yes the RPS are always at 1 or 2. |
I don't think that |
Thanks for this amazing tool, I was able to run it on my old machine but on this one I'm seeing the following error
This happens on portswigger labs or even google.com or example.com
I tried the
debug.py
script when I changeconcurrentConnections
from 1 to 5 it starts failing after a couple of requests.Changing Engine.THREADED to Engine.BURP fixes the problem.
Using the regular intruder with a pool of 30 also works fine, so I think it's something specific to TurboIntruder.
Any help would be great, thanks
Config
MacBook Air (M1, 2020)
The text was updated successfully, but these errors were encountered: