So I'm new to Fiddler, I'm using it on Linux via the AppImage download on Debian/Testing. I'm trying to use it to debug something on my Android phone. When I seelect `Capture and Inspect Traffic` -> `Remote Devices` -> `Android`, click Next, select my ethernet interface, I try and go (on my phone or another machine) to the IP & Port that it shows, but can't connect. When I check the host machine's opened ports, it shows it opened up on IPv6, not IPv4, even though it's showing the IPv4 local address. I can ping the host IPv4 address just fine, but doesn't look like Fiddler is opening up a port on it.
$ netstat -anp | grep -i 8866 tcp6 0 0 :::8866 :::* LISTEN 230864/Fiddler.WebU
1 Answer, 1 is accepted
Hi Aaron,
For visibility, I will repost the suggestion we just posted in our private thread.
The Fiddler Everywhere application utilizes IPv4-mapped IPv6 addresses, which may explain why the netstat command does not detect the actual IPv4 address. You can confirm this by testing an IPv4 request using curl. For instance:
curl -vk https://www.example.com -x [ipv4.address]:8866 --ipv4
Replace [ipv4.address] with the specific address you are targeting (while Fiddler is started and operates on port 8866).
That being said, the reason you cannot view traffic from your Android device may be different. It is possible that your Android device is not on the same subnet (Fiddler only functions with remote devices on the same network) or network restrictions are in place (for example, your network might restrict visibility for remote devices on certain ports).
You can also try to manually set the Fiddler proxy on your Android device and test if you are able to access the Fiddler proxy per the instructions given in the following article:
Regards,
Nick Iliev
Progress Telerik
Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.