METHOD to Make unlimited proxies at Zero Cost

[SonOfJat]

One Linux server 16.04 or 18.04 with 1GB RAM is required to create one proxy. You can get this from AWS for free for one year since Linux 16.04 and 18.04 servers are available under AWS free tier.

If you need multiple proxies then you can create multiple AWS accounts and create multiple proxies. I have been doing this for last 3 years and used these proxies on Jarvee to run Instagram accounts. But now a days instagram is very strict and these proxies are not good for IG but you can use for other purposes.

In case you don't want to create multiple AWS accounts then you can create maximum 4 proxies with one Linux server(if you want more than 4 then you'll need to talk to AWS customer support to get additional IPs), Here you'll need to pay for additional 3 IP addresses.


GUIDE for creating one proxy using one AWS Linux 16.04/18.04 INSTANCE-

Connect to linux server using putty or ssh and then run following commands -

1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address linux_public_ip
netmask 255.255.255.255
broadcast linux_public_ip

auto eth0:1
iface eth0:1 inet static
address linux_private_ip
netmask 255.255.255.255
broadcast linux_private_ip

2. service networking restart

3. apt-get update
4. apt-get upgrade
5. apt-get -y install fail2ban software-properties-common
6. apt-get install nano
7. apt-get install build-essential libevent-dev libssl-dev
8. cd /etc
9. wget https://github.com/z3APA3A/3proxy/archive/0.8.12.tar.gz
10. tar zxvf 0.8.12.tar.gz
11. rm 0.8.12.tar.gz
12. cd 3proxy-0.8.12
13. nano src/proxy.h and add this line somewhere in the file
#define ANONYMOUS 1

14. make -f Makefile.Linux
15. make -f Makefile.Linux install
16. mkdir log
17. cd cfg
18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[linux_public_ip] -e[linux_public_ip]
proxy -n -a -p3128 -i[linux_private_ip] -e[linux_private_ip]
flush

19. chmod 0777 3proxy.cfg
20. cd ..
21. nano scripts/rc.d/proxy.sh
Here you will need to modify some paths in line no- 14,23,24,36,37 (check screenshot)



22. sh scripts/rc.d/proxy.sh start.


GUIDE for creating multiple proxies using one AWS Linux 16.04/18.04 INSTANCE [NOTE: there will be additional charges for using additional IPs]-

For this, first you'll need to get additional IPs and then bind those IPs to your Linux instance. To get additional IPs, you can create a new network interface and get some elastic IP addresses. bind those elastic IPs to your secondary network interface and follow this guide to bind the secondary interface to your Linux/Ubuntu instance - https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/

One interface can have 2 IP addresses and AWS allows maximum two interfaces for one instance under free tier so one can create 4 Proxies.

when It is done then you have to run same commands except step 1 and step 18..

Step 1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address interface1_public_ip1
netmask 255.255.255.255
broadcast interface1_public_ip1

auto eth0:1
iface eth0:1 inet static
address interface1_private_ip1
netmask 255.255.255.255
broadcast interface1_private_ip1

auto eth0:2
iface eth0:0 inet static
address interface1_public_ip2
netmask 255.255.255.255
broadcast interface1_public_ip2

auto eth0:3
iface eth0:1 inet static
address interface1_private_ip2
netmask 255.255.255.255
broadcast interface1_private_ip2

auto eth1:0
iface eth0:0 inet static
address interface2_public_ip1
netmask 255.255.255.255
broadcast interface2_public_ip1

auto eth1:1
iface eth0:1 inet static
address interface2_private_ip1
netmask 255.255.255.255
broadcast interface2_private_ip1

auto eth1:2
iface eth0:0 inet static
address interface2_public_ip2
netmask 255.255.255.255
broadcast interface2_public_ip2

auto eth1:3
iface eth0:1 inet static
address interface2_private_ip2
netmask 255.255.255.255
broadcast interface2_private_ip2


Step 18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[interface1_public_ip1] -e[interface1_public_ip1]
proxy -n -a -p3128 -i[interface1_public_ip2] -e[interface1_public_ip2]
proxy -n -a -p3128 -i[interface1_private_ip1] -e[interface1_private_ip1]
proxy -n -a -p3128 -i[interface1_private_ip2] -e[interface1_private_ip2]
proxy -n -a -p3128 -i[interface2_public_ip1] -e[interface2_public_ip1]
proxy -n -a -p3128 -i[interface2_public_ip2] -e[interface2_public_ip2]
proxy -n -a -p3128 -i[interface2_private_ip1] -e[interface2_private_ip1]
proxy -n -a -p3128 -i[interface2_private_ip2] -e[interface2_private_ip2]
flush

 

[McJeff]

Not 100% free. AWS charges approximately $1 when you signup for card verification

Nice share nonetheless.

 

[SonOfJat]

Not 100% free. AWS charges approximately $1 when you signup for card verification

Nice share nonetheless.

Verification charges are refunded within next 2-3 days, and in my country it is 2 rupees only ( that's 0.027 USD)

 

[TheKingSlayer]

Not 100% free. AWS charges approximately $1 when you signup for card verification

Nice share nonetheless.

they don't, that's just authorization that vanishes within 5-7 business days

 

[McJeff]

Verification charges are refunded within next 2-3 days, and in my country it is 2 rupees only ( that's 0.027 USD)

they don't, that's just authorization that vanishes within 5-7 business days

Weird.. I never got a refund on my card, I assumed it is must be unrefundable.

 

[Winter_Wizard]

Does it work for some1? Seems like this method gets mixed reactions

 

[SonOfJat]

Does it work for some1? Seems like this method gets mixed reactions

I have been using this for three years . It will definitely work if it is followed step by step.

 

[Joker King]

Nice share Thanks it works!

 

[CyHead]

Unless you buy a dedicated IP, aren't most of these burned from abuse?

 

[SonOfJat]

Unless you buy a dedicated IP, aren't most of these burned from abuse?

That's what everyone used to say here and there but I used these proxies with Instagram for 2 years(2k18 and 2k19) without any issues, It stopped working only when instagram did some changes last year and none of static proxies work with IG anymore. I'm still using AWS proxies for some other purposes and it works fine.

 

[bdman]

do you have something for mobile proxy?
I mean, turn mobile ip to proxy

 

[SonOfJat]

do you have something for mobile proxy?
I mean, turn mobile ip to proxy

I have a software to create 4G proxies(in partnership with a dev guy), pretty cheap which I am also using. but you'll need to purchase your own hardware (one time cost). I'm planning to sale that software here on BHW very soon after purchasing Jr. VIP. You can use this app to create one 4g proxy - https://play.google.com/store/apps/details?id=com.proxidize (It's free)

 

[Shockx]

when i do nano /etc/network/interfaces the file just says
# ifupdown has been replaced by netplan(5) on this system. See
# /etc/netplan for current configuration.
# To re-enable ifupdown on this system, you can run:
# sudo apt install ifupdown
and when I run sudo apt install ifupdown nothing happens it just says

E: Unable to locate package ifupdown

 

[turelink]

nice share

 

[Whitewhistle]

Not to be a party popper, but won't your proxies get abused instantly? Of course, depending on how you use them.

 

[goku786]

One Linux server 16.04 or 18.04 with 1GB RAM is required to create one proxy. You can get this from AWS for free for one year since Linux 16.04 and 18.04 servers are available under AWS free tier.

If you need multiple proxies then you can create multiple AWS accounts and create multiple proxies. I have been doing this for last 3 years and used these proxies on Jarvee to run Instagram accounts. But now a days instagram is very strict and these proxies are not good for IG but you can use for other purposes.

In case you don't want to create multiple AWS accounts then you can create maximum 4 proxies with one Linux server(if you want more than 4 then you'll need to talk to AWS customer support to get additional IPs), Here you'll need to pay for additional 3 IP addresses.


GUIDE for creating one proxy using one AWS Linux 16.04/18.04 INSTANCE-

Connect to linux server using putty or ssh and then run following commands -

1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address linux_public_ip
netmask 255.255.255.255
broadcast linux_public_ip

auto eth0:1
iface eth0:1 inet static
address linux_private_ip
netmask 255.255.255.255
broadcast linux_private_ip

2. service networking restart

3. apt-get update
4. apt-get upgrade
5. apt-get -y install fail2ban software-properties-common
6. apt-get install nano
7. apt-get install build-essential libevent-dev libssl-dev
8. cd /etc
9. wget https://github.com/z3APA3A/3proxy/archive/0.8.12.tar.gz
10. tar zxvf 0.8.12.tar.gz
11. rm 0.8.12.tar.gz
12. cd 3proxy-0.8.12
13. nano src/proxy.h and add this line somewhere in the file
#define ANONYMOUS 1

14. make -f Makefile.Linux
15. make -f Makefile.Linux install
16. mkdir log
17. cd cfg
18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[linux_public_ip] -e[linux_public_ip]
proxy -n -a -p3128 -i[linux_private_ip] -e[linux_private_ip]
flush

19. chmod 0777 3proxy.cfg
20. cd ..
21. nano scripts/rc.d/proxy.sh
Here you will need to modify some paths in line no- 14,23,24,36,37 (check screenshot)
View attachment 160662


22. sh scripts/rc.d/proxy.sh start.


GUIDE for creating multiple proxies using one AWS Linux 16.04/18.04 INSTANCE [NOTE: there will be additional charges for using additional IPs]-

For this, first you'll need to get additional IPs and then bind those IPs to your Linux instance. To get additional IPs, you can create a new network interface and get some elastic IP addresses. bind those elastic IPs to your secondary network interface and follow this guide to bind the secondary interface to your Linux/Ubuntu instance - https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/

One interface can have 2 IP addresses and AWS allows maximum two interfaces for one instance under free tier so one can create 4 Proxies.

when It is done then you have to run same commands except step 1 and step 18..

Step 1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address interface1_public_ip1
netmask 255.255.255.255
broadcast interface1_public_ip1

auto eth0:1
iface eth0:1 inet static
address interface1_private_ip1
netmask 255.255.255.255
broadcast interface1_private_ip1

auto eth0:2
iface eth0:0 inet static
address interface1_public_ip2
netmask 255.255.255.255
broadcast interface1_public_ip2

auto eth0:3
iface eth0:1 inet static
address interface1_private_ip2
netmask 255.255.255.255
broadcast interface1_private_ip2

auto eth1:0
iface eth0:0 inet static
address interface2_public_ip1
netmask 255.255.255.255
broadcast interface2_public_ip1

auto eth1:1
iface eth0:1 inet static
address interface2_private_ip1
netmask 255.255.255.255
broadcast interface2_private_ip1

auto eth1:2
iface eth0:0 inet static
address interface2_public_ip2
netmask 255.255.255.255
broadcast interface2_public_ip2

auto eth1:3
iface eth0:1 inet static
address interface2_private_ip2
netmask 255.255.255.255
broadcast interface2_private_ip2


Step 18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[interface1_public_ip1] -e[interface1_public_ip1]
proxy -n -a -p3128 -i[interface1_public_ip2] -e[interface1_public_ip2]
proxy -n -a -p3128 -i[interface1_private_ip1] -e[interface1_private_ip1]
proxy -n -a -p3128 -i[interface1_private_ip2] -e[interface1_private_ip2]
proxy -n -a -p3128 -i[interface2_public_ip1] -e[interface2_public_ip1]
proxy -n -a -p3128 -i[interface2_public_ip2] -e[interface2_public_ip2]
proxy -n -a -p3128 -i[interface2_private_ip1] -e[interface2_private_ip1]
proxy -n -a -p3128 -i[interface2_private_ip2] -e[interface2_private_ip2]
flush

Thanks for this amazing share brother

 

[SonOfJat]

Not to be a party popper, but won't your proxies get abused instantly? Of course, depending on how you use them.

I used these proxies on Jarvee for 2 years without any problems. I guess no-one uses AWS proxies for instagram automation. Still using these for my stealth US paypal and cashapp accounts , No issues at all.

 

[astro2014]

One Linux server 16.04 or 18.04 with 1GB RAM is required to create one proxy. You can get this from AWS for free for one year since Linux 16.04 and 18.04 servers are available under AWS free tier.

If you need multiple proxies then you can create multiple AWS accounts and create multiple proxies. I have been doing this for last 3 years and used these proxies on Jarvee to run Instagram accounts. But now a days instagram is very strict and these proxies are not good for IG but you can use for other purposes.

In case you don't want to create multiple AWS accounts then you can create maximum 4 proxies with one Linux server(if you want more than 4 then you'll need to talk to AWS customer support to get additional IPs), Here you'll need to pay for additional 3 IP addresses.


GUIDE for creating one proxy using one AWS Linux 16.04/18.04 INSTANCE-

Connect to linux server using putty or ssh and then run following commands -

1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address linux_public_ip
netmask 255.255.255.255
broadcast linux_public_ip

auto eth0:1
iface eth0:1 inet static
address linux_private_ip
netmask 255.255.255.255
broadcast linux_private_ip

2. service networking restart

3. apt-get update
4. apt-get upgrade
5. apt-get -y install fail2ban software-properties-common
6. apt-get install nano
7. apt-get install build-essential libevent-dev libssl-dev
8. cd /etc
9. wget https://github.com/z3APA3A/3proxy/archive/0.8.12.tar.gz
10. tar zxvf 0.8.12.tar.gz
11. rm 0.8.12.tar.gz
12. cd 3proxy-0.8.12
13. nano src/proxy.h and add this line somewhere in the file
#define ANONYMOUS 1

14. make -f Makefile.Linux
15. make -f Makefile.Linux install
16. mkdir log
17. cd cfg
18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[linux_public_ip] -e[linux_public_ip]
proxy -n -a -p3128 -i[linux_private_ip] -e[linux_private_ip]
flush

19. chmod 0777 3proxy.cfg
20. cd ..
21. nano scripts/rc.d/proxy.sh
Here you will need to modify some paths in line no- 14,23,24,36,37 (check screenshot)
View attachment 160662


22. sh scripts/rc.d/proxy.sh start.


GUIDE for creating multiple proxies using one AWS Linux 16.04/18.04 INSTANCE [NOTE: there will be additional charges for using additional IPs]-

For this, first you'll need to get additional IPs and then bind those IPs to your Linux instance. To get additional IPs, you can create a new network interface and get some elastic IP addresses. bind those elastic IPs to your secondary network interface and follow this guide to bind the secondary interface to your Linux/Ubuntu instance - https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/

One interface can have 2 IP addresses and AWS allows maximum two interfaces for one instance under free tier so one can create 4 Proxies.

when It is done then you have to run same commands except step 1 and step 18..

Step 1. nano /etc/network/interfaces
add below content and save this file -

auto eth0:0
iface eth0:0 inet static
address interface1_public_ip1
netmask 255.255.255.255
broadcast interface1_public_ip1

auto eth0:1
iface eth0:1 inet static
address interface1_private_ip1
netmask 255.255.255.255
broadcast interface1_private_ip1

auto eth0:2
iface eth0:0 inet static
address interface1_public_ip2
netmask 255.255.255.255
broadcast interface1_public_ip2

auto eth0:3
iface eth0:1 inet static
address interface1_private_ip2
netmask 255.255.255.255
broadcast interface1_private_ip2

auto eth1:0
iface eth0:0 inet static
address interface2_public_ip1
netmask 255.255.255.255
broadcast interface2_public_ip1

auto eth1:1
iface eth0:1 inet static
address interface2_private_ip1
netmask 255.255.255.255
broadcast interface2_private_ip1

auto eth1:2
iface eth0:0 inet static
address interface2_public_ip2
netmask 255.255.255.255
broadcast interface2_public_ip2

auto eth1:3
iface eth0:1 inet static
address interface2_private_ip2
netmask 255.255.255.255
broadcast interface2_private_ip2


Step 18. nano 3proxy.cfg (save file with below content after modifying it)

#!/usr/local/bin/3proxy
daemon
pidfile /etc/3proxy-0.8.12/3proxy.pid
auth strong
nserver 8.8.8.8
nscache 65536
timeouts 1 5 30 60 180 1800 15 60
users [proxy_username]:CL:[proxy_password]
allow [proxy_username]
proxy -n -a -p3128 -i[interface1_public_ip1] -e[interface1_public_ip1]
proxy -n -a -p3128 -i[interface1_public_ip2] -e[interface1_public_ip2]
proxy -n -a -p3128 -i[interface1_private_ip1] -e[interface1_private_ip1]
proxy -n -a -p3128 -i[interface1_private_ip2] -e[interface1_private_ip2]
proxy -n -a -p3128 -i[interface2_public_ip1] -e[interface2_public_ip1]
proxy -n -a -p3128 -i[interface2_public_ip2] -e[interface2_public_ip2]
proxy -n -a -p3128 -i[interface2_private_ip1] -e[interface2_private_ip1]
proxy -n -a -p3128 -i[interface2_private_ip2] -e[interface2_private_ip2]
flush

Can someone here turn this into a guide for dummies like me?

I mean, this is for people with knowledge in linux and so on and although this interests me, I don't understand exactly what to do?

I think OP has assumed beforehand that EVERYONE knows linux and that is not the case. In fact, I would like to know how many people on this forum understand what is explained in the guide?

 

[salalba99]

thank you
can you tell me if i can do proxy port 443 ?

 

[SpivBlack]

thank you
can you tell me if i can do proxy port 443 ?

yes you can just need to get a ssl cert. Try letsencrypt[dot]org or any other ACME provider the Certs are free