Snawoot/hola-proxy

Error credservice.go - temporary ban detected

GGPay opened this issue · 12 comments

GGPay commented

Hello, thank you for awesome tool.

Starting 14-Jul -21 - i got an error indicate banned by hola.

Log server below

image

Snawoot commented

Hi!

Is it working though? I see fallback mechanism was fired and endpoint was received.

rany2 commented

Maybe we'd want to downgrade the level of the "temporary ban detected" to INFO so we don't confuse people.

olikami commented

Any request will fail with 407 Auth Failed suspicious:

PROXY   : 2021/07/15 10:47:23 handler.go:95: INFO     127.0.0.1:59105 GET http://2ip.ru/ 407 Auth Failed suspicious
rany2 commented

@olikami I spammed the API to trigger a ban on my machine and I could confirm that fallback mechanism stopped working

rany2 commented 
$ ./hola-proxy -proxy-type lum
MAIN    : 2021/07/15 13:48:18 main.go:147: INFO     hola-proxy client version v1.5.2 is starting...
MAIN    : 2021/07/15 13:48:18 main.go:148: INFO     Constructing fallback DNS upstream...
MAIN    : 2021/07/15 13:48:18 main.go:155: INFO     Initializing configuration provider...
CRED    : 2021/07/15 13:48:18 credservice.go:30: ERROR    Configuration bootstrap error: temporary ban detected. Retrying with the fallback mechanism...
MAIN    : 2021/07/15 13:48:32 main.go:168: INFO     Endpoint: https://zagent1251.hola.org:22225
MAIN    : 2021/07/15 13:48:32 main.go:169: INFO     Starting proxy server...
MAIN    : 2021/07/15 13:48:32 main.go:171: INFO     Init complete.
PROXY   : 2021/07/15 13:48:33 handler.go:104: INFO     Request: 127.0.0.1:40296 HTTP/1.1 GET http://ipinfo.io/
PROXY   : 2021/07/15 13:48:35 handler.go:95: INFO     127.0.0.1:40296 GET http://ipinfo.io/ 407 Auth Failed suspicious
PROXY   : 2021/07/15 13:48:37 handler.go:104: INFO     Request: 127.0.0.1:40300 HTTP/1.1 GET http://ipinfo.io/
PROXY   : 2021/07/15 13:48:38 handler.go:95: INFO     127.0.0.1:40300 GET http://ipinfo.io/ 407 Auth Failed suspicious
PROXY   : 2021/07/15 13:48:41 handler.go:104: INFO     Request: 127.0.0.1:40302 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:48:46 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp 167.71.189.124:22225: operation was canceled
PROXY   : 2021/07/15 13:48:46 handler.go:104: INFO     Request: 127.0.0.1:40306 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:49:16 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp 167.71.189.124:22225: i/o timeout
PROXY   : 2021/07/15 13:50:01 handler.go:104: INFO     Request: 127.0.0.1:40322 HTTP/1.1 CONNECT //ipinfo.io:443
PROXY   : 2021/07/15 13:50:08 handler.go:49: ERROR    Can't satisfy CONNECT request: dial tcp 167.71.189.124:22225: operation was canceled
PROXY   : 2021/07/15 13:50:10 handler.go:104: INFO     Request: 127.0.0.1:40326 HTTP/1.1 GET http://ipinfo.io/
  • 👍1
Snawoot commented

Not much we can do with it. Once your IP got bad reputation, you've three options:

  • Try to change your home IP. If your ISP offers a dynamic IP to you, it is sufficient to reboot your router.
  • Use other solution: opera-proxy, windscribe-proxy
  • Use hola-proxy in conjunction with windscribe-proxy or opera-proxy via hola-proxy's -proxy option to circumvent IP block. This may be useful if you still need residential IPs (-proxy-type lum) and opera-proxy or windscribe-proxy is not sufficient alone.
  • 👍1
rany2 commented

@Snawoot Would it be a good idea to disable the fallback mechanism now?

Snawoot commented

@rany2 I don't think so, it'll stop work in Egypt and other countries with censorship then. Basically fallback proxies introduced by hola exactly for censorship reasons. That fact it helped bypass Hola's per-IP limits for a while was just a nice side-effect.

  • 👍1
rany2 commented

@Snawoot I thought that the fallback proxies stopped working completely. Would be nice to add a flag to force fallback proxies to test if they actually still work

Snawoot commented

@rany2 Usually I've tested it with self-inflicted block adding

0.0.0.0         client.hola.org

to hosts file. I've tested it right now, it seem to work OK.

[15:19:25] dt1:~/src/hola-proxy> hola-proxy 
MAIN    : 2021/07/15 15:19:27 main.go:147: INFO     hola-proxy client version v1.5.1 is starting...
MAIN    : 2021/07/15 15:19:27 main.go:148: INFO     Constructing fallback DNS upstream...
MAIN    : 2021/07/15 15:19:27 main.go:155: INFO     Initializing configuration provider...
CRED    : 2021/07/15 15:19:27 credservice.go:30: ERROR    Configuration bootstrap error: Post "https://client.hola.org/client_cgi/background_init?uuid=8273196d6a2447c5af65e07e30da1348": dial tcp 0.0.0.0:443: connect: connection refused. Retrying with the fallback mechanism...
MAIN    : 2021/07/15 15:19:29 main.go:168: INFO     Endpoint: https://zagent1283.hola.org:22225
MAIN    : 2021/07/15 15:19:29 main.go:169: INFO     Starting proxy server...
MAIN    : 2021/07/15 15:19:29 main.go:171: INFO     Init complete.
PROXY   : 2021/07/15 15:19:37 handler.go:104: INFO     Request: 127.0.0.1:36040 HTTP/1.1 GET http://api.ipify.org/
PROXY   : 2021/07/15 15:19:38 handler.go:95: INFO     127.0.0.1:36040 GET http://api.ipify.org/ 200 OK
rany2 commented

That's surprising... so I guess they fixed their fallback mechanism to prevent block bypass.

GGPay commented

Thank you so much for prompt response. I found closed issue about ban detection after open my.
Really appreciate it.
I have an issue too with opera-proxy and windscribe-proxy - will open issue in their repo.