Skip to content

"Continuously try to post to a site even if failed before xx times"

Afternoon @Sven,

Is there any chance you could add in a little bit of code to the "Continuously try to post to a site even if failed before" feature where the user has the ability to set a max number of times you want SER to try hit the domain? For example the user enters 10 and SER will remember the number of times it has tried to hit a domain and when it gets to 10 it wont try that domain again unless the URL history is reset for that project?

Captcha costs are getting out of control on this new method I am developing and this feature would help me out loads rather than just having SER smash a domain over and over again when after say 10 fails even with human solved captchas it is safe to say a post will never get through.

I'm sure it will also help the wider community who are building their own lists when it comes to their wordpress scrapes, so many targets but such a tiny number will work with SER so it will save them cash on human solved captchas too.




  • Poor Sven has so much requests nowadays that he can't even go to the toilet :D
    Anyway this is a nice feature request and I think it not only benefits those who are building their own lists but those who are buying sitelists as well.
  • shaunshaun
    Yea defo mate, I am mainly using one of Looplines lists these days but then I push it through SER and filter it out into folders for specific tasks and this feature would be a massive help there. I know sven is busy but it would have been nice to have some feedback as to if he saw this as viable or not.
  • SvenSven
    added for next update.
  • shaunshaun
    Cheers :).
  • 710fla710fla ★ #1 GSA SER VERIFIED LIST
    Awesome suggestion was thinking of something similar
  • shaunshaun
    @710fla Been playing around with it on a few verification projects and keep seeing nice little uses for it :).

    @sven just out of curiosity what happens within SER once all domains hit the set limit? I have noticed that after about 15-20 minutes the log has loads of SockError Connection Refused error but if I Inactive/Active the project or restart SER it seems to go back to normal for about 15-20 minutes again.

    Any chance it could be linked?
  • SvenSven
    hmm naw that should not be a cause of restarting the project or has anything to do with this new option.
  • shaunshaun
    @sven I think I have worked it out. Will this new feature only knock one try off if the tool actually gets to submit or the site loads?

    I have been playing around and I think this might be whats happening when you press start, for easy of math lets say there is only 10 target sites.

    First loop - 10 targets
    3  verified.
    3 submitted.
    2 failed.
    2 sites offline so give the socket error.

    Second loop - 10 targets - (3 verified + 3 submitted) 4 sites remaining.
    1 verified.
    1 submitted
    2 sites offline.

    Third loop - 10 targets - (4 verified + 4 submitted) 2 sites remaining.
    2 sites offline.

    Fourth loop - 10 targets - (4 verified + 4 submitted) 2 sites remaining.
    2 sites offline.

    Fifth loop - 10 targets - (4 verified + 4 submitted) 2 sites remaining.
    2 sites offline.

    So as the alive sites are wittled down all that is left is offline sites and thus the log fills up with sock errors.

    Just a theory but could this be the cause?
  • SvenSven
    sorry for late reply. I must have missed your reply. Yes indeed thats the correct logic here.
Sign In or Register to comment.