Permanently Closed Marketplace Sales Thread

Status
Not open for further replies.
I think there's some problem with the proxy server. It harvested 30K proxies and only 80 live proxies found?
What's the problem?
 
Some things I would suggest to make it better:
1) Highlight which proxy type we chose either through an underline or check mark next to the proxy type list. Currently, no way to know.
2) Option of crawling of ONLY the proxy URL list specified in the config and turning off leechlist.
3) Find an IP. Create a feature to let us search for a IP within the proxy list panel.

Question:
1) Is there a way to run PM using a proxy? Don't want to piss off my ISP.
2) Why is PM going to a leechlist that falls outside the list specified in the config fetch URL? I would prefer this to be an option, rather than the rule. To test, I cleared the proxy fetching URL list. Stored only the HMA urls and attempted to crawl only the HMA pages and bring in only those scraped proxies. PM goes out to a leech list and pulls in proxies from them instead. I don't want that. I want the ability to control the URLs that PM crawls. So how does one force the crawler to scrape **ONLY** proxies in the config proxy URL list?

Hi, thanks for the great suggestions! :) We will consider adding the requests to our extensive feature base.

To answer your questions: 1. running PM behind a proxy will not please your ISP any more - the traffic is still passing through your ISP.
2. PM does scrape only the URLs in the config proxy URL list if your proxy list is empty. From our usage manual:

If your proxy list is empty, Proxy Multiply will scrape proxies from its list of 400+ websites that are updated daily with working proxies. (your Proxy Fetching URLs)


If you have proxies in the list already, Proxy Multiply will begin searching Google, Bing, Yahoo and other search engines to find more proxies using your existing proxy list as a search basis - thus how Proxy Multiply 'multiplies' one proxy into 5,000 or more!



Has this been done yet?

We have received numerous other requests/needs for updates and we are trying to work those into the same update w/ the ports. Thank you again for your patience :)

JRim:

I've seen this shit come up twice (see image below). This happens when launching PM fresh and getting new proxies. This domain/url is shipped with your product.

Are you aware of this? I've since removed that url out of my proxy URL list and suggest you check and ship proxy website URLs that have been tested regularly. That kind of thing could fuck things up for everyone.

If you try going to that URL directly, it shows that it is dead AND it tries an exploit.

Hey Hat, we do monitor the URLs regularly but we appreciate your help! :) The URL has been removed from the list.

noticed a problem on my windows server 2008 and win7 64 bit , when I start the program it asks for update , it then is stuck with waiting behind the waiting for program to close option in the update manager . I then closed the program using my task manager , second time it updated fine on both systems. Just something weird that I noticed and thought I would let you know

A security software or something of that nature on your PCs is preventing the updater from closing Proxy Multiply automatically. We apologize for the inconvenience.

I think there's some problem with the proxy server. It harvested 30K proxies and only 80 live proxies found?
What's the problem?

Hi udit, it is working well for us. If you're trying to find only Google-enabled proxies, they are the most rare and you should not expect more than 300-400 (with many factors in consideration). If this problem has been consistent for you, please try lowering your thread count (Configuration -> General tab -> lower the number of threads). :)


Thank you all for your continued support and suggestions! We love refining and shaping Proxy Multiply into the perfect software for our customers!
 
the program needs a way to auto delete all old proxies, 'get proxies', test proxies, then automatically export those proxies to a text file every X minutes.
 
Another idea I think would make the program better.

When using automation, after scanning the old proxies and going below the threshold of working proxies I think it would be good to have it use a random proxy from the working list to search for new ones instead of always using the same or first one.

Not sure if this is already being done but seems to me that if a random working one is used, it would normally find new/different lists to scan.
 
the program needs a way to auto delete all old proxies, 'get proxies', test proxies, then automatically export those proxies to a text file every X minutes.

Thanks! The next update is going to be feature-packed with all of these suggestions!

Another idea I think would make the program better.

When using automation, after scanning the old proxies and going below the threshold of working proxies I think it would be good to have it use a random proxy from the working list to search for new ones instead of always using the same or first one.

Not sure if this is already being done but seems to me that if a random working one is used, it would normally find new/different lists to scan.

Proxy Multiply does not re-use the same proxy to search with. So if it uses the first proxy right now to search, the next time it will use the second proxy, and so on and so forth. The proxy is marked as used to search with and will not be repeated for use with a search. :)
 
Any idea on when this next release will be out? I only have a couple days left on my trial and would like to see if the "filter out certain ports" option is going to work well enough for me to buy it?
 
I'm also interested in the new version as well. I'm looking for a solid proxies program to scrape proxies and I still don't know what to choose between ProxyMultiply and ... THE OTHER :)
 
Another nice feature would be;

When it is using proxies in the list to find other proxies to have the option to have it only search for pages/proxies posted within a certain time frame.
For instance when I look for proxy lists manually I don't really want to scrape proxies from a list that was posted over a year ago because 99% of those will be dead and I'd just be wasting my time by even scanning that list.
So what I do is narrow my search down to lists posted in the last week or less.
Granted I don't find as many proxy lists this way but I always find more working proxies by doing this.
Below is a screenshot in case anyone isn't following what I'm suggesting here.

wwwgooglecomscreencaptu.png
 
kickapooh you are right and this is a great feature indeed. If I rember well.. GSA Search Engine Ranker have in its own proxy scrapper a function like this.. to search only in a given time frame.

Also I think there shold be done some cleaning in proxies list. Coz the program starts fine find new proxies but after checking 10000 mostof them are dead and barely find working ones. So is obvious there are some outdated lists outhere that do not bring any proxies just old dead ones that only add up junk to the list and consume time.

I think the key is to find the most lucrative proxy lists and get rid of old outdated ones.

Also I'm wondering is there a function to be able to upload 2 lists instead of one?! I want to upload on FTP a list with annonimty proxies and another one with Google friendly one.
 
This software seems like a life saver for many.

Noob question - i need proxies for youtube activities, my guess is that i do need G-enabled proxies, right? Do they need to be elite or anonymus, HTTP or socks? Can someone be kind and explain me what proxies will work for YT to save me some precious time?

Thanks
 
ISSUE #1: Public proxy
I scraped 100,000 proxies. Left PM running and took 5 hours to test. Only 375 working proxies out of a worldwide list. Less than 1% useful SUCKS!

ISSUE #2: PM goes to a leech list = CRAP PROXIES

What do you mean by proxy list being empty? I read the manual and saw that blurb in there. I always clear the proxy list (right click, clear) before getting proxies.

I ticked the "View URLs used for proxy fetching..." Closed down PM. Started it up again. Zero items in the queue. No proxies showing in the table. Hit Get proxies button. After it finished the popup showed that you went to the leech list scraping URLs. Why? It was empty.

I then tested further. I went to the proxy fetch url list and chose only HMA urls. Cleared the list. Imported HMA list. Saved. Hit Get proxies. After it was done, the popup showed that you went to the leech list to pull proxies. The status window said that you found 90 more websites starting with the first IP address as the baseline. I looked at the prixies in the queue. I then looked at the HMA website to compare what was on the pages with what was in the queue. I didn't find any in the queue.

YOU NEED TO FIX THIS SHIT

If I specify HMA only scraped proxies, thats what I should get. Not some other crap from search engines and leech lists put into the list.
 
Last edited:
Another nice feature would be;

When it is using proxies in the list to find other proxies to have the option to have it only search for pages/proxies posted within a certain time frame.
For instance when I look for proxy lists manually I don't really want to scrape proxies from a list that was posted over a year ago because 99% of those will be dead and I'd just be wasting my time by even scanning that list.
So what I do is narrow my search down to lists posted in the last week or less.
Granted I don't find as many proxy lists this way but I always find more working proxies by doing this.
Below is a screenshot in case anyone isn't following what I'm suggesting here.

wwwgooglecomscreencaptu.png

Good thinking :) We utilize a handful of search engines and some do not support such methods but we will certainly add said feature where applicable.

kickapooh you are right and this is a great feature indeed. If I rember well.. GSA Search Engine Ranker have in its own proxy scrapper a function like this.. to search only in a given time frame.

Also I think there shold be done some cleaning in proxies list. Coz the program starts fine find new proxies but after checking 10000 mostof them are dead and barely find working ones. So is obvious there are some outdated lists outhere that do not bring any proxies just old dead ones that only add up junk to the list and consume time.

I think the key is to find the most lucrative proxy lists and get rid of old outdated ones.

Also I'm wondering is there a function to be able to upload 2 lists instead of one?! I want to upload on FTP a list with annonimty proxies and another one with Google friendly one.

Very true; some pages are updated less frequently than others. Uploading 2 files via FTP is currently not an option.

This software seems like a life saver for many.

Noob question - i need proxies for youtube activities, my guess is that i do need G-enabled proxies, right? Do they need to be elite or anonymus, HTTP or socks? Can someone be kind and explain me what proxies will work for YT to save me some precious time?

Thanks

Hi, you do not need Google enabled proxies. We will add a YouTube filter to the next version, but until then, you can create your own YT filter by clicking Configuration -> HTTP Proxy Testing -> Check against specific site -> configure it for http://youtube.com/ for the URL and set the content to check for to "YouTube" (no quotes).
 
proxycrap.jpg (zoom in with browser to see details)

JRim: Are you going to fix this or not? As far as I am concerned this is a pain in the ass. Your tool is delivering crap proxies outside what the user specifies. The list is clearly empty and PM is bringing in these leech lists to pull info to front the result list.

The maximum proxie limit specified in the config should be a ceiling, not an obligation to fill the queue with the number specified in that config parameter. In other words, the urls specified in the fetch list dictate what should be returned. You should not intermingle going outside that list unless the user requests it. I would suggest putting in a checkbox to allow us to control this called "fetch outside this list".

This is like me going to a search engine to search for "dog collars" and I set the result set to Max at 1000 items. The search engine gives me 500. Then, you go out (without my approval) and fetch 500 items of more garbage and include in the result. Give me the results *I* want, not what you want to give me.

Besides, the leech list you are using can become stale. We don't get to modify this list because you are bringing it in by default on every run. If the items in this crappy leech list don't get updated often, the processing time takes even longer searching the same crap list every run. Don't force your user to have to do this and waste CPU processing time. Make this alternative list an option. Better yet, don't even use it. Let your users choose and fill in the fetch list themselves.
 
Last edited:
I scraped 150,000 proxies too. Gave me 386 anonymous proxies which is pretty disappointing.

Then, strangely, kept going for another 150,000 and still 386 anonymous proxies. So 300,000 tested and 386 proxies. Took me about 4 hours. Damn...

Can't someone find some better starting sources so that we don't get so many dead proxies?
 
I've been testing Proxy Multiply and the results are less than pleasing. Out of 1.5 million ip addresses, I found one that was fast and consistently passed the test in scrabebox.
 
View attachment 12033 (zoom in with browser to see details)

JRim: Are you going to fix this or not? As far as I am concerned this is a pain in the ass. Your tool is delivering crap proxies outside what the user specifies. The list is clearly empty and PM is bringing in these leech lists to pull info to front the result list.

The maximum proxie limit specified in the config should be a ceiling, not an obligation to fill the queue with the number specified in that config parameter. In other words, the urls specified in the fetch list dictate what should be returned. You should not intermingle going outside that list unless the user requests it. I would suggest putting in a checkbox to allow us to control this called "fetch outside this list".

This is like me going to a search engine to search for "dog collars" and I set the result set to Max at 1000 items. The search engine gives me 500. Then, you go out (without my approval) and fetch 500 items of more garbage and include in the result. Give me the results *I* want, not what you want to give me.

Besides, the leech list you are using can become stale. We don't get to modify this list because you are bringing it in by default on every run. If the items in this crappy leech list don't get updated often, the processing time takes even longer searching the same crap list every run. Don't force your user to have to do this and waste CPU processing time. Make this alternative list an option. Better yet, don't even use it. Let your users choose and fill in the fetch list themselves.

Many users requested that PM automatically queries search engines afterwards. I think you are confused and the confusion is creating frustration. I understand that is not how you want it to work but the general majority of users want it to work in that fashion. Just to reiterate how the software works: after it scrapes your initial URL fetching list, it then moves on to search Google/Bing/Yahoo for more proxies. That is what is occurring in your screenshot. That is how PM produces a never-ending list of proxies. If you do not want it to do that, hit the 'Stop' button after it says 'Fetched XXX proxies from URLs' (after it finishes scraping). It is not scraping from its own URL list after, it's scraping from what the search engines give it.

I scraped 150,000 proxies too. Gave me 386 anonymous proxies which is pretty disappointing.

Then, strangely, kept going for another 150,000 and still 386 anonymous proxies. So 300,000 tested and 386 proxies. Took me about 4 hours. Damn...

Can't someone find some better starting sources so that we don't get so many dead proxies?

Hmm. Proxy Multiply currently works as such: it queries from a list of predefined URLs, scraping 10-15k proxies. After it finishes that scrape, it turns on its "search" mechanism, searching Google/Bing/Yahoo for more proxies using the proxies you scraped as a search query. PM will be changed to instead TEST the initial scrape list first so you are only using WORKING proxies as your search criteria instead of all of the proxies. THis should significantly improve proxy scraping.

I've been testing Proxy Multiply and the results are less than pleasing. Out of 1.5 million ip addresses, I found one that was fast and consistently passed the test in scrabebox.

1.5 million? Did you generate those at random or scrape them? If they were generated, that is the issue. If you scraped them, you have an issue with your configuration. PM me with a screenshot of your configuration window.
 
Any idea on when this next release will be out? I only have a couple days left on my trial and would like to see if the "filter out certain ports" option is going to work well enough for me to buy it?
While I like the software so far I never got a response from you and my trial has ended. Just lost a sale bro. Customer support and frequency of updates are what I look for before buying software. I know you guys have your hands full but they don't have to all be implemented at the same time. Take it one update at a time, release it and start on the next.
 
You're telling me you are too lazy to do 5 minutes of coding to put in a checkbox option to turn search engine leeching off?

Look, this feature is NOT working. You are generating totally crap proxies and wasting everyone's time. Already your users are telling you that this strategy does not work. Out of 100,000+ proxies we are getting less than 400. That is a 0.4% success rate. Its even worse after we test the proxies. Less than 1/2 of them are of any use factoring in that every else is vying for those proxies. So we are left with a 0.2% success rate for 5 fucking hours of processing.

We shouldn't have to deal with this by default.

Every person who does not use a port scanner to generate their own list, leeches off every one else's public list. If you don't keep that leech list fresh, you are just handing us more shit proxies and wasting our time. It is more work for you keeping that list fresh, and your users are going to continue to hit this thread with complaints.

Your leech urls should be a suggestion, not a requirement.

Also don't forget that we are risking our ISP accounts here. By processing more shit proxies, we are increasing our time on the pipe and taking on more risk from getting our accounts banned.

If you aren't producing at least a 5% success rate on 100,000 proxies, you need a better strategy.

Whats even more questionable, is after you are done processing, your View url box asks us if we want to save the leech list that is generating 99% of crap. Why even ask that if we are forced to use it anyway.

Put in a checkbox and let us turn this on/off. Leave it on by default if that is what you want. But for the rest of us who don't want to waste our time, let us have the choice to turn it off.
 
Last edited:
It's a great idea, searching for ip numbers to find more ip numbers...You might find me 50 proxies that pass your test, but when I test them with scrapebox, they all fail. And your automated feature doesn't seem to save files or send emails either.

Here is my config:
Screen shot 2012-05-19 at 9.53.23 PM.pngScreen shot 2012-05-19 at 9.39.39 PM.png
 
Last edited:
You're telling me you are too lazy to do 5 minutes of coding to put in a checkbox option to turn search engine leeching off?

Look, this feature is NOT working. You are generating totally crap proxies and wasting everyone's time. Already your users are telling you that this strategy does not work. Out of 100,000+ proxies we are getting less than 400. That is a 0.4% success rate. Its even worse after we test the proxies. Less than 1/2 of them are of any use factoring in that every else is vying for those proxies. So we are left with a 0.2% success rate for 5 fucking hours of processing.

We shouldn't have to deal with this by default.

Every person who does not use a port scanner to generate their own list, leeches off every one else's public list. If you don't keep that leech list fresh, you are just handing us more shit proxies and wasting our time. It is more work for you keeping that list fresh, and your users are going to continue to hit this thread with complaints.

Your leech urls should be a suggestion, not a requirement.

Also don't forget that we are risking our ISP accounts here. By processing more shit proxies, we are increasing our time on the pipe and taking on more risk from getting our accounts banned.

If you aren't producing at least a 5% success rate on 100,000 proxies, you need a better strategy.

Whats even more questionable, is after you are done processing, your View url box asks us if we want to save the leech list that is generating 99% of crap. Why even ask that if we are forced to use it anyway.

Put in a checkbox and let us turn this on/off. Leave it on by default if that is what you want. But for the rest of us who don't want to waste our time, let us have the choice to turn it off.

Hi, looking forward to hearing your feedback after the revised search/test mechanism (mentioned above) due today...

While I like the software so far I never got a response from you and my trial has ended. Just lost a sale bro. Customer support and frequency of updates are what I look for before buying software. I know you guys have your hands full but they don't have to all be implemented at the same time. Take it one update at a time, release it and start on the next.

Sorry to hear that but real life gets in the way of matters as I'm sure you can understand. Update will be issued by end of day today. If you would like to private message me your authorization key displayed when you start the program, you will receive a free extension to your trial.

It's a great idea, searching for ip numbers to find more ip numbers...You might find me 50 proxies that pass your test, but when I test them with scrapebox, they all fail. And your automated feature doesn't seem to save files or send emails either.

Hi, it has been well-noted (on this very forum nonetheless) that SB's proxy testing mechanism is flawed. We recommend directly importing the proxies into S/Box without re-testing. If a proxy passes the 'Google' test in PM, it was able to perform a Google search. If you have Scrapebox queries that are too robotic (too much robot syntax), you will get any proxy banned quickly. Regarding the automation critique, if you never meet 100 proxies (as is your case), in the current version of PM it will never finish its automation cycle. However, in the update due this evening, PM will perform the post-automation e-mail/txt file write at the end of each test in the automation cycle as customers are having issues with the threshold concept. :)
 
Status
Not open for further replies.
Back
Top