pry0cc / axiom

The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
MIT License
4k stars 622 forks source link

add more timeouts when creating fleets #567

Closed marcelo321 closed 2 years ago

marcelo321 commented 2 years ago

When creating fleets in linode with a number above 10 I tend to get code 429 "too many requests" and I have to run the command again with the amount of linodes I actually want.

Would it be possible to add some extra timeouts in the creation of fleets?

┌errors─┬───────────────────┐
│ field │ reason            │
├───────┼───────────────────┤
│       │ Too many requests │
└───────┴───────────────────┘
0xtavian commented 2 years ago

https://github.com/pry0cc/axiom/issues/566

Was just brought up again earlier today. There are a good amount of issues asking for this. I just don’t know when I’ll have the time to do it.

0xtavian commented 2 years ago

@marcelo321 can you update to the latest code and try again?

marcelo321 commented 2 years ago

Hi @0xtavian, I updated it axiom-update and I don't seem to get the 403 error anymore, but I still do get errors when trying to create e.g 12 instances.

INITIALIZING IN 5 SECONDS, CTRL+C to quit... 
Instances: [ javis01 javis02 javis03 javis04 javis05 javis06 javis07 javis08 Request failed: 408
┌errors─┬──────────────────┐
│ field │ reason           │
├───────┼──────────────────┤
│       │ Please try again │
└───────┴──────────────────┘
javis09 javis10 javis11 javis12  ]
Request failed: 408leet javis initialization...
┌errors─┬──────────────────┐
│ field │ reason           │
├───────┼──────────────────┤
│       │ Please try again │
└───────┴──────────────────┘

btw I appreciate you taking the time to look at it

0xtavian commented 2 years ago

Hey @marcelo321 thanks for testing. did all the instance spin up regardless of errors?

marcelo321 commented 2 years ago

@0xtavian,

definitely improved but I think 2-3 instances didn't set up, so out of 12 I think 9 were up correctly.

edit: just run it again creating 12 instances and got 0 errors, all instances were ok. <3

pdelteil commented 2 years ago

I also had this issue, can confirm it works great now.