A Few Questions: Using a VPS+Proxies for 24/7 Botting

[kashisking]

Hey guys, as the title says, I'm a bit hung up on the logistics of running a bot with proxies and a vps.

Right now I am using digital ocean which allows only one IP per droplet, as I understand, that means one proxy per droplet. The cheapest droplet is $5 per month so that adds up pretty quick even with just 30 private proxies because each would need a separate vps.

Am I missing something here? Are the guys working with 200-300 proxies all paying for separate vps per each 1-2 proxies? And how would I handle running a bot across multiple vps's? I know thats quite a few questions I just feel like im in the dark here.

Thanks in Advance

 

[X]

Unless I'm reading this wrong, you only need one VPS with one IP (though the more the merrier, depending on how hard you're botting and the resources required).

Most bots have proxy support so you just need to rent a batch of proxies and plug them into the tool(s) on the VPS so you can utilize the IP addresses from the proxy supplier.

 

[jazzc]

I'm gonna make your day.

a) Go to OVH, get the cheapest hourly public cloud instance. Then order 32 failover IPs for it (it's a one time fee, for ever).

b) Now get the smallest "sandbox" instance. Migrate the failover IPs to it. Delete the other instance.

You now have 32 IPs on a $3/month vps. Setup a proxy software and use the proxies on your main VPS.

Edit: Start with ordering 1 IP to get the ropes of it, then go full ahead.

 

[blackwalker]

OVH would be a good host for this, try them out.

 

[kashisking]

Unless I'm reading this wrong, you only need one VPS with one IP (though the more the merrier, depending on how hard you're botting and the resources required).

Most bots have proxy support so you just need to rent a batch of proxies and plug them into the tool(s) on the VPS so you can utilize the IP addresses from the proxy supplier.

I'm gonna make your day.

a) Go to OVH, get the cheapest hourly public cloud instance. Then order 32 failover IPs for it (it's a one time fee, for ever).

b) Now get the smallest "sandbox" instance. Migrate the failover IPs to it. Delete the other instance.

You now have 32 IPs on a $3/month vps. Setup a proxy software and use the proxies on your main VPS.

Edit: Start with ordering 1 IP to get the ropes of it, then go full ahead.

OVH would be a good host for this, try them out.

Thanks guys, that really does clear up my confusion and will get on OVH today.
Cheers

 

[kashisking]

I'm gonna make your day.

a) Go to OVH, get the cheapest hourly public cloud instance. Then order 32 failover IPs for it (it's a one time fee, for ever).

b) Now get the smallest "sandbox" instance. Migrate the failover IPs to it. Delete the other instance.

You now have 32 IPs on a $3/month vps. Setup a proxy software and use the proxies on your main VPS.

Edit: Start with ordering 1 IP to get the ropes of it, then go full ahead.

Jazz,
This recommendation did indeed make my day so thank you, just a few things I am unclear on if you have the time. Concerning OVH, is a General Purpose Public Cloud Instance good or would CPU be better? And by "Setup a proxy software and use the proxies on your main VPS" do you mean using the OVH Public Cloud Instance in my Digital Ocean Droplet or doing everything within the OVH Public Cloud Instance?
Cheers

 

[jazzc]

Concerning OVH, is a General Purpose Public Cloud Instance good or would CPU be better? And by "Setup a proxy software and use the proxies on your main VPS" do you mean using the OVH Public Cloud Instance in my Digital Ocean Droplet or doing everything within the OVH Public Cloud Instance?

Yes, the idea is that you're going to make your own proxies, using the ovh IPs originally bought via their public cloud offering (and then migrated into their cheap sandbox instance). For that you need a) the IPs and b) some proxy software installed on sandbox to utilize them (for example, "tinyproxy"). When all is done, you would use the proxies in your software in your DO instance.

If you're not technical, I suggest paying a few $ to a freelance linux admin/power user to have the technical side set up - isn't worth your time figuring all this out from scratch.

 

[stiger]

I'm gonna make your day.

a) Go to OVH, get the cheapest hourly public cloud instance. Then order 32 failover IPs for it (it's a one time fee, for ever).

b) Now get the smallest "sandbox" instance. Migrate the failover IPs to it. Delete the other instance.

You now have 32 IPs on a $3/month vps. Setup a proxy software and use the proxies on your main VPS.

Edit: Start with ordering 1 IP to get the ropes of it, then go full ahead.

This is amazing.

Thank you!

 

[YesAndNo]

Yes, the idea is that you're going to make your own proxies, using the ovh IPs originally bought via their public cloud offering (and then migrated into their cheap sandbox instance). For that you need a) the IPs and b) some proxy software installed on sandbox to utilize them (for example, "tinyproxy"). When all is done, you would use the proxies in your software in your DO instance.

If you're not technical, I suggest paying a few $ to a freelance linux admin/power user to have the technical side set up - isn't worth your time figuring all this out from scratch.

You might as well mention @kashisking how easy will be for the site to ban his whole subnet if all of his ips come from OVH. But that is okay, let him spend all of his money on cheap ips from OVH so he can learn a painful lesson that proxies from the same subnet, even the same datacenter are easy to block by the site being targeted.

 

[jazzc]

You might as well mention @kashisking how easy will be for the site to ban his whole subnet if all of his ips come from OVH. But that is okay, let him spend all of his money on cheap ips from OVH so he can learn a painful lesson that proxies from the same subnet, even the same datacenter are easy to block by the site being targeted.

Don't be so butthurt when you see people sharing nice tricks.

 

[YesAndNo]

Don't be so butthurt when you see people sharing nice tricks.

Not butthurt at all, but if you look at the OP's first post, then your trick will hurt him more in the long run.

You can't put all of your eggs in one basket when using proxies. So your OVH trick is easily bypassed by blocking the IP range, because OVH will give you proxies that are in close proximity to each other.

My advice to the OP is to follow @jazzc advice of using setting up your own proxies with tinyproxy.But please do not buy all of your ips from one provider such as OVH. Even if they are cheap, because they are very easy to block if they all come from the same place. If you are going to get 32 ips, then spread them at least to 4-5 different providers.


Also, your "forever 1 time fee" assumption is not really true. Given OVH's track record and how recently they have increased their prices by 20% across multiple of their services, plus their DDOS pricing hikes , makes me believe that their $3 dollar setup fee will soon go away.

OVH is funded by a lot of VC money, and those VC's want to see a return.

 

[stuna]

I'm gonna make your day.

a) Go to OVH, get the cheapest hourly public cloud instance. Then order 32 failover IPs for it (it's a one time fee, for ever).

b) Now get the smallest "sandbox" instance. Migrate the failover IPs to it. Delete the other instance.

You now have 32 IPs on a $3/month vps. Setup a proxy software and use the proxies on your main VPS.

Edit: Start with ordering 1 IP to get the ropes of it, then go full ahead.

Thats what I was looking for.. THANKS

 

[EsperanzaHorne]

thanks for this useful information...

 

[jazzc]

but if you look at the OP's first post, then your trick will hurt him more in the long run.

I thanked your post because the rest you wrote is reasonable advice in general. But this line above, isn't. See the OP's first post - his original plan was to buy more DO droplets. I gave him a way to get the same grade of ips, but way cheaper. I wouldn't have suggest the same if he was looking for other types. But it is clear that his current use doesn't require anything sophisticated. If and when it does, he will seek the appropriate workaround and perhaps someone will be there to give him pointers.

 

[YesAndNo]

If and when it does, he will seek the appropriate workaround and perhaps someone will be there to give him pointers.

I guess you are right. Looking back at his post, he was going to spend an awful a lot of money on DigitalOcean ips, which made 0 sense. However, the OVH trick just makes his original intentions 10-15 times cheaper a year term. So I think it will lessen the damage done to his wallet and when the times comes he will look for more sophisticated setups.


By the way @kashisking if you are going to use Tinyproxy make sure you edit the config file to make the proxy anonymous. Look for tinyproxy config anonymous on google. Good luck!