residential proxy not always
andrew-delph opened this issue · 4 comments
Im trying to use this proxy to make connnections with omegal.com.
I am able to make connections when using the chrome extension but no luck when using this proxy server.
Any suggestions would be greatly appreciated.
docker run --rm -it \
--security-opt no-new-privileges \
-p 127.0.0.1:8080:8080 \
--name hola-proxy \
yarmak/hola-proxy:latest -proxy-type lum -country us -list-proxies
MAIN : 2023/05/29 20:09:03 main.go:190: WARNING Detected latest extension version: "1.211.139". Pass -ext-ver parameter to skip resolve and speedup startup
Login: user-uuid-d44fa342f9c9480e87627e6c2b688faf
Password: 9aa32ff1879b
Proxy-Authorization: basic dXNlci11dWlkLWQ0NGZhMzQyZjljOTQ4MGU4NzYyN2U2YzJiNjg4ZmFmOjlhYTMyZmYxODc5Yg==
host,ip_address,direct,peer,hola,trial,trial_peer,vendor
zagent1614.hola.org,45.76.165.215,22222,22223,22224,22225,22226,vultr
zagent1611.hola.org,45.63.17.124,22222,22223,22224,22225,22226,vultr
zagent1620.hola.org,45.77.146.122,22222,22223,22224,22225,22226,vultr
I think the issue is to do with the proxies connecting to a datacenter and not a residential IP.
Attempting fixes here: #13
If you have any suggestions on this, it would be greatly appreciated.
$curl -x localhost:8080 http://2ip.io
164.92.69.130
$ curl -x localhost:8080 http://2ip.ru
104.28.57.218
confirmed that calling 2ip.ru is using the peer network
Hi, @andrew-delph
It would be nice if you'll be able to reproduce correct behavior with browser extension and use chrome://net-export/
to dump your requests and see which address and, more important, port was used in these requests. This way it will be more clear how correct proxied request looks like and what to do about it