" -limit uint" option no longer works for uint>3 ...
Vangelis66 opened this issue · 2 comments
Thanks a lot for this very versatile and extremely useful tool/app! 👍
It would appear that the -limit uint flag no longer has any effect on the -list-proxies flag when uint>3, because the latter then always prints just 3 proxies, no matter the value of uint 😞 ...
-list-proxies in fact implies -limit 3 (default behaviour, as per documentation); -limit 1 & -limit 2 seem to still work, but any number above 3 will simply result in the default 3 proxies...
hp.exe = renamed hola-proxy.windows-386.exe
Logs:
hp -version && hp -country gb -list-proxies -limit 2 =>
v1.5.6
Login: user-uuid-1479fb8bd4c840b9b009f161a206dedc
Password: 8e382ad04da5
Proxy-Authorization: basic dXNlci11dWlkLTE0NzlmYjhiZDRjODQwYjliMDA5ZjE2MWEyMDZkZWRjOjhlMzgyYWQwNGRhNQ==
host,ip_address,direct,peer,hola,trial,trial_peer,vendor
zagent2625.hola.org,188.166.170.182,22222,22223,22224,22225,22226,digitalocean
zagent2622.hola.org,165.22.118.161,22222,22223,22224,22225,22226,digitalocean
... and:
hp -version && hp -country gb -list-proxies =>
v1.5.6
Login: user-uuid-7c4ff879404340d393f22a28d3ade7a8
Password: d9f032aa5aef
Proxy-Authorization: basic dXNlci11dWlkLTdjNGZmODc5NDA0MzQwZDM5M2YyMmEyOGQzYWRlN2E4OmQ5ZjAzMmFhNWFlZg==
host,ip_address,direct,peer,hola,trial,trial_peer,vendor
zagent2513.hola.org,134.122.96.196,22222,22223,22224,22225,22226,digitalocean
zagent2623.hola.org,206.189.19.206,22222,22223,22224,22225,22226,digitalocean
zagent2510.hola.org,64.227.47.181,22222,22223,22224,22225,22226,digitalocean
... but:
hp -version && hp -country gb -list-proxies -limit 30 =>
v1.5.6
Login: user-uuid-4b457a04221b471da4dabd851fc37cfc
Password: 2b4f27e35cbe
Proxy-Authorization: basic dXNlci11dWlkLTRiNDU3YTA0MjIxYjQ3MWRhNGRhYmQ4NTFmYzM3Y2ZjOjJiNGYyN2UzNWNiZQ==
host,ip_address,direct,peer,hola,trial,trial_peer,vendor
zagent2507.hola.org,134.122.96.27,22222,22223,22224,22225,22226,digitalocean
zagent2629.hola.org,165.22.118.163,22222,22223,22224,22225,22226,digitalocean
zagent2625.hola.org,188.166.170.182,22222,22223,22224,22225,22226,digitalocean
The issue isn't specific to proxies of a certain country, gb has been selected here just as an example...
FTR, ca. one year ago, hp -country gb -list-proxies -limit 30 had produced below result (kept on disk as log):
Login: user-uuid-fa9f2d867f5e4116a6615ff7bd196d4c
Password: b23103648ef3
Proxy-Authorization: basic dXNlci11dWlkLWZhOWYyZDg2N2Y1ZTQxMTZhNjYxNWZmN2JkMTk2ZDRjOmIyMzEwMzY0OGVmMw==
host,ip_address,direct,peer,hola,trial,trial_peer,vendor
zagent1325.hola.org,45.32.176.142,22222,22223,22224,22225,22226,vultr
zagent1328.hola.org,95.179.203.192,22222,22223,22224,22225,22226,vultr
zagent384.hola.org,134.209.23.13,22222,22223,22224,22225,22226,digitalocean
zagent381.hola.org,178.128.41.38,22222,22223,22224,22225,22226,digitalocean
zagent387.hola.org,134.209.23.138,22222,22223,22224,22225,22226,digitalocean
zagent1348.hola.org,104.238.174.106,22222,22223,22224,22225,22226,vultr
zagent1416.hola.org,46.101.93.168,22222,22223,22224,22225,22226,digitalocean
zagent320.hola.org,209.97.138.73,22222,22223,22224,22225,22226,digitalocean
zagent1346.hola.org,104.238.172.103,22222,22223,22224,22225,22226,vultr
zagent119.hola.org,45.77.228.82,22222,22223,22224,22225,22226,vultr
zagent1317.hola.org,45.76.130.208,22222,22223,22224,22225,22226,vultr
zagent321.hola.org,178.128.38.157,22222,22223,22224,22225,22226,digitalocean
zagent632.hola.org,134.209.30.17,22222,22223,22224,22225,22226,digitalocean
zagent1329.hola.org,45.63.100.82,22222,22223,22224,22225,22226,vultr
zagent391.hola.org,157.245.36.181,22222,22223,22224,22225,22226,digitalocean
zagent1399.hola.org,188.166.146.125,22222,22223,22224,22225,22226,digitalocean
zagent318.hola.org,165.22.115.49,22222,22223,22224,22225,22226,digitalocean
zagent1337.hola.org,209.250.228.28,22222,22223,22224,22225,22226,vultr
zagent1342.hola.org,45.76.131.21,22222,22223,22224,22225,22226,vultr
zagent630.hola.org,167.172.61.124,22222,22223,22224,22225,22226,digitalocean
zagent1400.hola.org,188.166.144.209,22222,22223,22224,22225,22226,digitalocean
zagent1412.hola.org,209.97.129.10,22222,22223,22224,22225,22226,digitalocean
zagent1203.hola.org,178.62.11.71,22222,22223,22224,22225,22226,digitalocean
zagent1409.hola.org,188.166.146.170,22222,22223,22224,22225,22226,digitalocean
zagent1349.hola.org,192.248.146.105,22222,22223,22224,22225,22226,vultr
zagent442.hola.org,95.179.198.237,22222,22223,22224,22225,22226,vultr
zagent1405.hola.org,188.166.146.122,22222,22223,22224,22225,22226,digitalocean
zagent113.hola.org,78.141.242.183,22222,22223,22224,22225,22226,vultr
zagent1309.hola.org,45.77.225.111,22222,22223,22224,22225,22226,vultr
zagent1304.hola.org,192.248.161.66,22222,22223,22224,22225,22226,vultr
The issue is caused by some change on Hola's end 😡, because it can be reproduced even with older hola-proxy versions, that used to work back then...
In the hope this can be, somehow, dealt with, many thanks for your great efforts thus far 😄 👍 ...
I can confirm it's from the Hola side -- can't do anything about that, sorry.
Thanks for your attention and quick reply 😄 ; it's indeed unfortunate nothing can be done on the app's side to mitigate this hola-instigated 😡 unwelcome change 😭 ...
In view of that, perhaps it should be wise to modify hola-proxy -h's output (with regard to the two involved options) to read something like:
-list-proxies
output proxy list (default -limit 3) and exit
-limit uint (implies -list-proxies)
amount of proxies in retrieved list (maximum 3, even for uint>3)