connection not private error on android chrome
See original GitHub issueSteps to reproduce the problem:
I have installed certificate using this method on android (https://github.com/mitmproxy/mitmproxy/issues/2054#issuecomment-327735569) So before week mitmproxy works fine, google had opened successfully in android chrome browser but today i tried to open google it said your connection is not private i also clear user credential, and update mitmproxy v4, reinstalled certificate but still getting error that your connection is not private.
Any other comments? What have you tried so far?
Removed Certificate, reinstalled using adb method
tried --ssl-insecure
not work
System information
Mitmproxy: 4.0.1 binary Python: 3.6.3 OpenSSL: OpenSSL 1.1.0h 27 Mar 2018 Platform: Linux-4.13.0-43-generic-x86_64-with-debian-stretch-sid
./mitmdump
10.42.0.204:53930: CONNECT www.google.co.in:443
<< Cannot establish TLS with client (sni: www.google.co.in): TlsException("(-1, 'Unexpected EOF')",)
10.42.0.204:53930: clientdisconnect
10.42.0.204:53931: clientconnect
10.42.0.204:53932: clientconnect
10.42.0.204:53931: CONNECT www.google.co.in:443
<< Cannot establish TLS with client (sni: www.google.co.in): TlsException("(-1, 'Unexpected EOF')",)
10.42.0.204:53931: clientdisconnect
10.42.0.204:53933: clientconnect
10.42.0.204:53932: CONNECT www.google.co.in:443
<< Cannot establish TLS with client (sni: www.google.co.in): TlsException("(-1, 'Unexpected EOF')",)
10.42.0.204:53932: clientdisconnect
10.42.0.204:53933: CONNECT www.google.co.in:443
<< Cannot establish TLS with client (sni: www.google.co.in): TlsException("(-1, 'Unexpected EOF')",)
10.42.0.204:53933: clientdisconnect
10.42.0.204:53934: clientconnect
10.42.0.204:53934: CONNECT www.google.com:443
<< Cannot establish TLS with client (sni: www.google.com): TlsException("(104, 'ECONNRESET')",)
10.42.0.204:53934: clientdisconnect
10.42.0.204:53935: clientconnect
10.42.0.204:53935: CONNECT clients4.google.com:443
<< Cannot establish TLS with client (sni: clients4.google.com): TlsException("(104, 'ECONNRESET')",)
10.42.0.204:53935: clientdisconnect
10.42.0.204:53936: clientconnect
10.42.0.204:53937: clientconnect
10.42.0.204:53936: POST http://event.apiv9.com/event.php
<< 200 OK 33b
10.42.0.204:53937: CONNECT www.google.com:443
<< Cannot establish TLS with client (sni: www.google.com): TlsException("(-1, 'Unexpected EOF')",)
10.42.0.204:53937: clientdisconnect
10.42.0.204:53936: POST http://event.apiv9.com/event.php
<< 200 OK 33b
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Your Connection is not Private Error - Fix it on Anroid and ...
In PC: Press Ctrl + Shift + Delete and clear the data. ; In a Mobile Phone: Chrome menu → Settings → Privacy...
Read more >How to Solve "Your Connection is Not Private" Error on Android
Here's how to fix “Your Connection is Not Private” error · 1. Invalid Date & Time: · 2. Try to open the site...
Read more >How to Fix "Your Connection Is Not Private" Error - Hostinger
If you see the “Your connection is not private” warning message, you should first try to reload the page. While this might seem...
Read more >How to Fix a Connection-Is-Not Private Error - Lifewire
How to Fix it When Your Connection Isn't Private · Double-check the website address. · Reload the web page. · Check your device's...
Read more >Fix connection errors - Google Chrome Help
Check the web address for typos. Make sure your internet connection is working normally. Contact the website owner. Get help with a specific...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is likely caused by this error NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM I am seeing this error in Desktop Chrome browser, google recently updated Chrome to now allow SHA-1 certificates. They need to be updated. I presume they update the Chrome on Android as well.
Recent mitmproxy releases generate proper certificates, so the fix here is to 1) update mitmproxy, 2) delete ~/.mitmproxy, 3) start mitmproxy, and 4) install the new certificate.