Replies: 1 comment 1 reply
-
still dont get why only mitm is the only one that doesnt work with this specific website, have tried charles works , burp works |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Problem Description
A clear and concise description of what the bug is.
Steps to reproduce the behavior:
log:
[15:13:32.001][127.0.0.1:57575] client connect [15:13:32.028][127.0.0.1:57573] server connect vin.vehiculo.com.mx:443 (3.210.59.147:443) [15:13:32.525][127.0.0.1:57580] client connect [15:13:32.576][127.0.0.1:57580] server connect www.google.com:443 ([2607:f8b0:4012:826::2004]:443) [15:13:32.681][127.0.0.1:57568] server connect regularizaauto.sspc.gob.mx:443 (201.116.142.142:443) [15:13:32.758][127.0.0.1:57568] Server TLS handshake failed. Certificate verify failed: unable to get local issuer certificate [15:13:32.759][127.0.0.1:57568] Unable to establish TLS connection with server (Certificate verify failed: unable to get local issuer certificate). Trying to establish TLS with client anyway. If you plan to redirect requests away from this server, consider setting
connection_strategyto
lazyto suppress early connections. [15:13:32.767][127.0.0.1:57568] server disconnect regularizaauto.sspc.gob.mx:443 (201.116.142.142:443) [15:13:32.937][127.0.0.1:57583] client connect
System Information
Paste the output of "mitmproxy --version" here.
Mitmproxy: 10.2.2 binary
Python: 3.12.1
OpenSSL: OpenSSL 3.1.4 24 Oct 2023
Platform: Windows-10-10.0.19045-SP0
everything else is working fine however it doesnt work with this one
Beta Was this translation helpful? Give feedback.
All reactions