[NPS] NiX Proxy Suite looking for testers and translators

[NIXMY]

On linux, one checking thread takes about 75kB of RAM because PHP CLI version has ANSI C style fork(). On GUI versions (Windows/Linux), one checking thread takes 7-14MB of RAM because it has to fork whole PHP process under Apache. So 10 threads will require about 150MB in the worst case . This the only flipside of coin but I can't do anything about it because it's web application. Still I think features, reliability and speed will forgive this issue. Said memory usages applies to the proxy checker. Proxy leecher is done different way and consumes very low amount of memory.

mic141414: You're in testers. No worries mate. I need to do everything myself, including the product page and banners. I just need more time. Maybe I should not promise anything when it comes to ETA's but im quite confident that within a day or two im very close to send the new version.

 

[NIXMY]

I've sent 1.1.2 version to all current testers. Just check your messages. Depending on your feedback I am ready to release this tool very soon. Stay tuned for the next update. There are still various features to be coded that did not made into this release.

I've just verified that when using 10 threads and 5 sub-threads (the default settings), NPS is faster than Charon with 100 threads

I'll update asap. introduction video and screenshots to reflect the latest update at my site.

 

[mic141414]

thank you for the update

I can see some new features already

* leeched sites with a green check marked (verified) so i am guessing sites checked if alive (cool)
* proxy checker can work now with a txt import file (really cool)

I have sent you an email .. i will then begin to test everything again

 

[NIXMY]

Here is the introduction video that reflects the latest updates: http://myproxylists.com/NPS.mp4

There will be soon hotfix update that will fix a few minor issues. You guessed a green check mark almost right, with hotfix version it will auto-disable any source that was dead without deleting it, that allows you re-verify and you can decide whether or not to delete that source.

The next update will have a powerful proxy scanning options. NPS power has been totally unleashed once I am done with that update.

PS. I still recommend to verify any source manually with your browser JS disabled before adding it. It's a bad practice to add sources without verifying them first.

 

[mic141414]

yes you are right i just wanted to check the leecher quickly so now i will pay more attention to the sources i want to add

PS. I still recommend to verify any source manually with your browser JS disabled before adding it. It's a bad practice to add sources without verifying them first.

 

[mic141414]

i have an error i didnt get with previous version

This webpage has a redirect loop
The webpage at http://127.0.0.1/nps/index.php?p=user&tool=proxy-leecher&action=sources has resulted in too many redirects.

<<Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects>>

I deleted my sources then got that error
I reloaded http://127.0.0.1/nps deleted my proxie (3 lists) and got the error again
and now got it almost every time i try to do something
Maybe something on my end ... any idea please ?

 

[mic141414]

first test (i have a slow connection i think)

i imported a proxies list : 5561
TOTAL PROCESS TIME : 0:00:47:15
WORKING PROXIES: 862

threads : 25. Subtreads : 5. autodetection

 

[NIXMY]

I've just received translations for tooltips, and was about to start updating those texts. I'll look into that redirect problem, I haven't had redirect loops but I never emptied sources list. I did not had redirect issues when I was testing the latest version. Let me also reload and then I can reproduce all possible errors.

What comes to that proxycheck, I think your version is still in 'Evaluation' mode, did you added a license key to 'General settings' in the admin control panel? It does not lift the the limits before you do so.

Edit: Upon deleting sources it will indeed end up in infinite redirect loop. Fixing. According to my tests, infinite loop applies only to the sources and this is already fixed in my development version. Expect in an hour or two hotfix release.

PS. You're able to backup easily for example your current leech list via XAMP's PMA package, just select NIX_PS database and use the 'Export' option. If you have already done so, just re-import your backup and you're set.

 

[mic141414]

i checked and and i have "Licensed Copy"

Cool happy to find bugs .. at least like that it can be fixed

What comes to that proxycheck, I think your version is still in 'Evaluation' mode, did you added a license key to 'General settings' in the admin control panel? It does not lift the the limits before you do so.

Edit: Upon deleting sources it will indeed end up in infinite redirect loop. Fixing. According to my tests, infinite loop applies only to the sources and this is already fixed in my development version. Expect in an hour or two hotfix release.

 

[NIXMY]

I suggest you to increase sub-threads, use something like 20. 47 minutes sounds still way too high though. If you can send me this 5,5k list, i can check it it using 25/5 thread to verify. Please also tell me me your other timeouts. No need to worry, I will not steal your proxies

25 threads is approx. 20k proxy /hour but of course your connection has to be stable and also the faster the proxy judge, the better. For example when I check proxies, I use my own judge because I know the server is stable and is hosted on a stable dedicated 100mbit connection.

 

[mic141414]

connection timeout 2
timeout 10
25/5 threads

i use the default judge

My proxy list +5K: http://www.mediafire.com/?okpd134h14pvrm6

I suggest you to increase sub-threads, use something like 20. 47 minutes sounds still way too high though. If you can send me this 5,5k list, i can check it it using 25/5 thread to verify. Please also tell me me your other timeouts. No need to worry, I will not steal your proxies

25 threads is approx. 20k proxy /hour but of course your connection has to be stable and also the faster the proxy judge, the better. For example when I check proxies, I use my own judge because I know the server is stable and is hosted on a stable dedicated 100mbit connection.

 

[NIXMY]

The default judge is hosted in Finland which is actually good because it is between USA/Asia and Finland is very well routed, always been according to my experience in the past decade.

PS. Only NPS support that judge, I don't want whole world proxy users use it.

 

[NIXMY]

connection timeout 2


timeout 10
25/5 threads

i use the default judge

My proxy list +5K: http://www.mediafire.com/?okpd134h14pvrm6

I tested with those settings on windows and you was right, it took about 47 minutes. After that I ran another test using 20/20 threads and it took 22 minutes. With this check I got 874 working proxy.

Finally I did a test at full speed (100/50 threads) and it took 10 minutes and 22 seconss. I got 942 working proxies with this check. So currently windows version can check about 30k proxy /hour

I had the protocol auto-detection on for both tests. Just increase threads.

I'll verify soon on Linux using the same threads to see is there difference.

PS. I've released fixed 1.1.3 version.

 

[LeviathanW]

Hi,

I've ran in some installation issues...
I followed your guide and put the files in the right place, and imported the sql tables. However, when accessing the page through the browers, I get

Error: cURL version 7.24 or newer is required to run the software

The version in xampp is 7.21.

As far as I understand, you need to recompile php with the latest curl. So I've installed the xampp developer package, downloaded the php source and the curl source package. Compiling php with the configure-options of xampp is not that easy apparently. I keep running in different dependency errors (missing source files for certain extensions that are in the php configure option).

I also tried downloading the precompiled curl file, and just change the file in the xampp folder. That didn't work. I tried changing the curl.config so it said it was version 7.26 (latest version), but that hadn't got any effect either.

I think you can just change a dll file on windows, so that would be an easier fix.

Weird that I am the only one who ran in that problem? I am trying to run it in Debian, with xampp 1.7.7 (latest non-beta version, but the beta has the same version cURL).

 

[mic141414]

i tried to run it on my shared hosting but Curl version was below the one required and host didn't want to upgrade

So i installed Xampp on my pc .. and i just replaced the curl file with the one OP provided in the script and it worked. My advice would be to delete everything ..start clean and retry but NIXMY will give you better advice.

PS: Received new update .. i will test later today and post results (i will increase threads to see difference)

 

[NIXMY]

I would recommend source compile for all linux users because you get the latest versions faster than any distribution updates their package versions. Of course this is more work. If we don't count me, you're the first tester to try it on Linux. I am using the latest source versions on my test linux (of course). Here's the deal, I would not recommend mixing source compile and the package versions as this will cause nothing but trouble. Therefore you must choose: Use only source-compile or the package versions.


I've sent you for now a version that allows cURL 7.21. Let me know how it went.

 

[mic141414]

test 06/14
same list proxies as yesterday 5561

Connection timeout [?] : 3
Connection timeout [?] : 10
threads: 60
subthread : 30

operation completed in 30min 22 sec.
759 good proxies

 

[LeviathanW]

NIXMY, I didn't receive any new mail, could you check?

I might try the compiling from source. Apache, php and mysql is all that is necessary?

 

[NIXMY]

I sent you a PM. You must also compile curl from source to get the latest version. I suggest you to use the version that allows curl 7.21. I am not going to start supporting source compiles, if you choose linux, you must be able to handle it on your own.

 

[LeviathanW]

Ok, redownloaded it, I'll be trying it tonight.
And no problem for not supporting the source compile stuff, that would get a bit off topic