can you hellp The process is very slow and eventually the error appears
CRITICAL] considerable lagging has been detected in connection response(s). Please use as high value for option '--time-sec' as possible (e.g. 10 or more)

--level=3 --risk=3 --no-cast --tamper=between --time-sec 15 --keep-alive --no-escape --random-agent
This is not an issue, the problem its probably with your network due to how time-based SQLi works you need to don't stress your conection that means avoid downloads, streaming an any high bandwith operation while you are doing the time-based attack
Are you sure of this thing
What solution if master "raigorx"
The solution is simple don't do anything else with your network while you are doing the attack.
Or maybe do you have any connection issue
My brother I did not work on my network through my server

The english is clear its looks like the target has a WAF/IPS/IDS that mean it is blocking your attack
This is not a network issue, it's the URL. It has nothing to do with his network. Get off your proxy or VPN and try it again
On Jun 19, 2017, at 1:44 AM, raigorx notifications@github.com wrote:
The english is clear its looks like the target has a WAF/IPS/IDS that mean it is blocking your attack
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Ekultek
How to do it
if you belive there was an exploitable things, perhaps it is time-base blind..
try using a network as close as possible to the targets.
WAF/IPS/IDS is just a guess from sqlmap, try use tools such as wafw00f to detect posibility of WAF
if WAF was detected you can use the correct 'tamper' parameter to bypass
Can you type the correct skip command
use option --technique=BEUS to skip time-based
--level=5 --technique=T --time-sec=1 -b --answers="redirect to=N,extending provided risk=N,keep testing the others=N" --technique=BEUS time-based
Is this formula true
It's not my responsibility to teach you how to exploit things if you don't know how to do it, you shouldn't be doing it. Try manual and then try sqlmap this issue should be closed as invalid.
On Jun 19, 2017, at 3:53 AM, shado notifications@github.com wrote:
--level=5 --technique=T --time-sec=1 -b --answers="redirect to=N,extending provided risk=N,keep testing the others=N" --technique=BEUStime-based
Is this formula true
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
Ekultek
Thank you brother, I am pleased to talk to you
Not trying to be rude or anything man, but the point of exploiting and hacking and all that good stuff is to figure out how everything works, to learn. If you can't do it and are asking for help then you're not learning anything. You need to try yourself, this issue should be your last resort, last ditch effort. Good luck to you, it seems to me that the URL probably is rejecting your proxy, or your VPN. There's a slight chance that there's a firewall sqlmap isn't picking up, but that's a very slight chance. I'd try it without a proxy, or vpn and see what happens. Try doing it manually. Hell you could use the payloads created by sqlmap as your tests for manual injection (under the xml directory). Hope it works out for you man.
On Jun 19, 2017, at 5:43 AM, shado notifications@github.com wrote:
Ekultek
Thank you brother, I am pleased to talk to you—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
Everything that @Ekultek says and also try to get the WAF and test it with tampers or write your own.
Most helpful comment
Not trying to be rude or anything man, but the point of exploiting and hacking and all that good stuff is to figure out how everything works, to learn. If you can't do it and are asking for help then you're not learning anything. You need to try yourself, this issue should be your last resort, last ditch effort. Good luck to you, it seems to me that the URL probably is rejecting your proxy, or your VPN. There's a slight chance that there's a firewall sqlmap isn't picking up, but that's a very slight chance. I'd try it without a proxy, or vpn and see what happens. Try doing it manually. Hell you could use the payloads created by sqlmap as your tests for manual injection (under the xml directory). Hope it works out for you man.