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
Expected behavior: traffic should flow through mitmproxy. Actual behavior:ERR_CONNECTION_RESET. Notes:
I can see the mitmproxy system CA certificate listed under Trusted credentials
http://mitm.it also yields the same ERR_CONNECTION_RESET error.
Quitting mitmproxy and trying to make requests again yields ERR_PROXY_CONNECTION_FAILED, which means the connection seems to be going through the proxy.
Turning off the proxy settings on the emulator makes pages load again (without flowing through mitmproxy, of course).
The event logs only show the client connecting/disconnecting:
For what it's worth, I just learned about android's 10.0.2.2 magic IP address, which does make the proxy work. Now I'm not sure if this problem is on the android side or mitmproxy. On one hand, the proxy works with the magic IP, but on the other hand, I can reach my local IP address from the emulator just the same (i.e. without any proxy settings, I can visit my local ip on a browser and make successful requests), so the network seems fine. 🤷
Problem Description
Setting up mitmproxy on a default android-33 emulator always yields a connection reset error, regardless of HTTP or HTTPS.
Steps to reproduce the behavior:
avdmanager create avd --name mitm --package 'system-images;android-33;default;arm64-v8a' -c 2048M -d pixel --force
mitmproxy
Expected behavior: traffic should flow through mitmproxy.
Actual behavior:
ERR_CONNECTION_RESET
.Notes:
mitmproxy
system CA certificate listed underTrusted credentials
http://mitm.it
also yields the sameERR_CONNECTION_RESET
error.mitmproxy
and trying to make requests again yieldsERR_PROXY_CONNECTION_FAILED
, which means the connection seems to be going through the proxy.The event logs only show the client connecting/disconnecting:
System Information
The text was updated successfully, but these errors were encountered: