Check outputted proxy list more frequently

[gamingmaster42]

Hello,
I am trying to set NHSEO to read the proxies from an outputted file more frequently. I set it at 5 minutes, but it appears on updates this is set to 10 minutes. I want to reduce this as I'm using it in conjunction with No Hands Proxies, so I want to read the proxies as frequently as possible, any suggestions.
Thanks

[jimbobo2779]

I had set the time to 1 minute a few updates back but there was a piece of code that was reverting it back to the old input time. I have removed this and the change will be present in the next update.

[gamingmaster42]

Thanks, but actually I think I misinterpreted this, the setting "Check Proxies every X mins" this enables the proxy checker to see if they are working, not load the file.
What I was looking for is the "Load file Delay" I think, I've lowered this to a minute (60000 ms) but not sure if it is pulling in the proxies at that rate.

[gamingmaster42]

Also, just tried something, not sure if this is a bug. I kept getting "Bad Search Proxy: 123.12.12.12:8080" (for example) using No Hands Proxies so I just straight up disabled proxies, but now I am getting: "Bad Search Proxy: " with no IP. Sent you an email hopefully you got it.

[jimbobo2779]

When NHSEO says "Bad Search Proxy: XXX.XXX.XXX.XXX:YY" it means that proxy has been burnt due to too many searches, if it says "Bad Search Proxy:" and you are not using proxies it means that your IP has been burnt due to too many searches.

If you are using more than 1 search thread and/or just searching Google or Yahoo (instead of both) your IP will get burnt out very quickly. Simply use proxies and lower the number of threads, use both Google and Yahoo and you will get less fails and more targets returned.

In the update after next I will be adding more search engines to lower the chance of IPs getting burnt as quickly. The next update is adding more posting features and platforms, I will also change the message for when no proxy is being used to more accurately point out that it is the users IP that is burnt out and how to improve this.

[gamingmaster42]

Thanks for the reply. That makes sense. I was running 2 search threads, so now I have reduced that to one.
Still, I guess my problem then is why No Hands Proxies seems to be telling me that I am getting Google passed proxies, then outputs these proxies into the file, but when No Hands SEO tries to search using them, it tells me that it is a bad search proxy. Any suggestions on how to fix that?

--
Well never mind. I think it is probably just a problem of certain proxies, looks like it's good now. Though I wish it could get more proxies, but this is probably because I have limited it in terms of threads (In No Hands Proxies I am using 10 threads because my machine is 1.25 GB RAM), so I've adjusted NHP to 15 threads and reduced the number of posting threads so it won't be too much on the VPS. Looks like it is time for a machine upgrade

[gamingmaster42]

Sorry to bump this, but this is kind of a related note on the "Bad Search Proxy".
I'm seeing in the logs, NHS says Bad Search Proxy, then something with %22% around the keyphrase for example - %22%i got 96 tears in 96 eyes%22% Now, I understand that %22% is the encoding for double quotes. However for the past few days I'm seeing any keywords surrounded by this, generally results in 0 targets and NHS keeps trying to get targets from these same keywords. Any way around that? Thanks

[jimbobo2779]

That is because you have "Exact keyword search" checked in the Settings=>More tab (Misc. Settings group of controls), uncheck this and save the settings and there will be no more jobs like this added for searching.

[gamingmaster42]

Thank you for your fast response. I have just disabled that, but still finding these kinds of entries in the log.

[jimbobo2779]

It will till the search job queue is finished, when the next search job list is created no more exact searches should be made. You can speed this up by disabling all profiles and then enabling them again. That should clear the search job queue.