You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 24, 2024. It is now read-only.
Step 3 gives [ERROR] Got HTTP 502: Bad Gateway at the terminal. In mitmproxy, you get
129.105.62.136:36544: clientconnect
129.105.62.136:36544: Cannot establish TLS with 74.125.127.105:443 (sni: None): TlsException('Cannot validate certificate hostname without SNI',)
129.105.62.136:36544: clientdisconnect
Step 4 returns at the terminal:
-Cannot connect to Google.
Error: Error on response:Error: tunneling socket could not be established, cause=connect EINVAL 0.0.31.144:80 - Local (0.0.0.0:0) : undefined
Step 5 returns Please check your internet connectivity... in the terminal. In mitmproxy, you get mitmproxy:
129.105.62.136:52310: clientconnect
129.105.62.136:52310: Client Handshake failed. The client may not trust the proxy's certificate for www.google.com.
129.105.62.136:52310: clientdisconnect
Any other comments? What have you tried so far?
Some thoughts:
Maybe these command-line tools aren't finding certificates.
The SNI error is weird - that seems like an upstream problem with googler.
Maybe my root certificate isn't properly installed.
System information
Operating system: (e.g. Linux Mint 18)
The text was updated successfully, but these errors were encountered:
aniketpanjwani
changed the title
Googler, how2, and socli command line tools don't work.
Googler, how2, and socli command line tools don't work while Chomper is running.
Feb 28, 2018
I had uninstalled Chrome and Firefox and only used a text browser. I then reinstalled Chrome and imported the mitmproxy certificate. When I did this, googler and socli continued to give the same problems they had been giving, but how2 began to function properly. This suggests that how2 uses Chrome's certificate database.
I think it's best to think of these as upstream errors, but I'm going to leave the issue open until it gets solved, because I expect others using Chomper will face similar problems.
I also think Googler's failure to provide SNI is probably a design failure of Googler. This may be arising because it doesn't use requests, and instead uses the http library.
Steps to reproduce the problem:
chomper allon 10
.googler python help
.how2 -l python remove from list
.socli python remove from list
.Step 3 gives
[ERROR] Got HTTP 502: Bad Gateway
at the terminal. In mitmproxy, you getStep 4 returns at the terminal:
Step 5 returns
Please check your internet connectivity...
in the terminal. In mitmproxy, you get mitmproxy:Any other comments? What have you tried so far?
Some thoughts:
System information
Operating system: (e.g. Linux Mint 18)
The text was updated successfully, but these errors were encountered: