2at2 / proxyChecker

Builds anonymous and alive proxy list.
1 stars 1 forks source link

panic: http2: server sent GOAWAY and closed the connection; #2

Open shirakun opened 5 years ago

shirakun commented 5 years ago
04 06:13:05.127102 ┇ Sending http://197.159.23.174:39150 @checker
04 06:13:05.127068 ┃ Proxy http://190.36.84.2:8080 @checker
04 06:13:05.127717 ┣ Error request - Get http://abc.com/checker: proxyconnect tcp: dial tcp 190.36.84.2:8080: connect: connection timed out @checker
04 06:13:06.433356 ┇ Response http://88.87.72.181:39928 @checker
04 06:13:06.433839 ┇ Sending http://51.38.185.54:3128 @checker
04 06:13:06.433769 ┃ Proxy http://88.87.72.181:39928 @checker
04 06:13:06.434776 ┃ Good proxy http://88.87.72.181:39928 @checker
04 06:13:07.372274 ┇ Response http://203.77.252.250:31988 @checker
04 06:13:07.372704 ┇ Sending http://118.174.196.39:54779 @checker
04 06:13:07.372533 ┃ Proxy http://203.77.252.250:31988 @checker
04 06:13:07.373471 ┃ Good proxy http://203.77.252.250:31988 @checker
04 06:13:07.430649 ┇ Response http://119.101.115.174:9999 @checker
04 06:13:07.431236 ┇ Sending http://124.41.252.22:8080 @checker
04 06:13:07.431097 ┃ Proxy http://119.101.115.174:9999 @checker
04 06:13:07.432121 ┣ Error request - Get http://abc.com/checker: proxyconnect tcp: dial tcp 119.101.115.174:9999: connect: connection timed out @checker
04 06:13:07.547997 ┇ Response http://169.56.29.164:8080 @checker
04 06:13:07.548281 ┇ Sending http://165.16.113.205:53281 @checker
04 06:13:07.548670 ┃ Proxy http://169.56.29.164:8080 @checker
04 06:13:07.603548 ┣ Failed process - http2: server sent GOAWAY and closed the connection; LastStreamID=2147483647, ErrCode=NO_ERROR, debug="" @checker
panic: http2: server sent GOAWAY and closed the connection; LastStreamID=2147483647, ErrCode=NO_ERROR, debug=""

goroutine 1 [running]:
main.main()
        /root/proxyChecker/checker/main.go:93 +0x169b
2at2 commented 5 years ago

Hi! You should run target/main.go at your server. Checker should connect to your target using proxy. The target will respond with some information about request and checker will make decision about proxy.

shirakun commented 5 years ago

Hi! You should run target/main.go at your server. Checker should connect to your target using proxy. The target will respond with some information about request and checker will make decision about proxy.

I wrote a new validation tool using PHP to mimic target I want to point out that checkers often have exceptions leading to exit (https://github.com/2at2/proxyChecker/issues/1) In php, I can catch exceptions and skip over the parts where exceptions occur Can't golang do that?