Yo, i recently made a config that bypasses cloudflare using FlareSolver, but it’s very slow and consumes too much ram, Since CF Cookies can be used multiple times from the same ip, isn’t there a way to run the firesolver part, so it solves the cf cookie, and it uploads that cf cookie somewhere so i can use it with other config?
i was planning on making a website for this, but maybe there’s a better way, what do you think?
it’s kinda hard to understand but i’ll try implementing it
Edit: With how flaresolver works i don’t think i could make the logic for the token
i get the cookie via requests
Maybe i can explain myself better with this image?
you can use IF to check if you have a valid CF Cookie. IF you do have a valid CF Cookie you then use JUMP to skip the flaresolverr block
how? to get the cf cookie it first has to be solved, so i’m not sure how you’d check if the cookie is valid before even having it
If i had a cf cookie that didn’t change i could do that, since i could check it before the solving part arrives
You would have to at least do 1 run with the flaresolverr to get a cookie. After that, you add it to a variable. You can then use the same cookie repeatedly until it gets blocked. At that point, you would want to use JUMP to return to the start of the config to get another CF Cookie.
When I use flaresolverr I don’t use globals, I usually write the cookie to a txt document and then just read it. Once that cookie expires or gets blocked I will have the config JUMP to the section that gets another cookie. And then the cycle just repeats.
If you need an example I can make one.
If you could pass me an example i’d be thankful
EDIT: I think i made it, i just have to fix a issue i have when using JUMP
What can i do so only 1 bot gets the cookie, because when i have the config running with 50 bots, it tries to get 50 tokens at time and it crashes OB
ig i can run another instance
You can try something like this
if(data.BOTNUM == 0){
LOG "GET COOKIE"
}
else
{
LOG "JUMP AWAY AND WAIT FOR COOKIE"
}
Using BotNum you can restrict a section of the config to 1 thread