I have installed and reinstalled fiddler but when I start fiddler I the initial checkup.aspx load in it but then it never gets any more traffic. I have tried multiple browsers but I never get any traffic.
I'm I missing a setting?
Nick Iliev
Telerik team
commented on 20 Aug 2021, 07:26 AM
There might be multiple reasons why you are not able to capture traffic. You should verify that Fiddler is set as a system proxy (when capturing is turned on) and that you have the administrative rights to update the OS system proxy, that the application you are monitoring is using the system proxy (and if not that it is explicitly set to use the Fiddler proxy), that you have enabled decryption of HTTPS traffic and that you have installed and trusted the root certificate. Additionally, some specific network configurations like VPN or security tools might also be causing side effects.
The above said we would need some more information about your specific network setup and about the application you are trying to monitor. Also is there any traffic being captured in your browsers, or is it a specific endpoint causing the issue?
Found the issue. When I deleted the old and reinstalled I did not realize it kept my old settings, on of which was a filter I had used. I removed the filter and everything worked as expected
There might be multiple reasons why you are not able to capture traffic. You should verify that Fiddler is set as a system proxy (when capturing is turned on) and that you have the administrative rights to update the OS system proxy, that the application you are monitoring is using the system proxy (and if not that it is explicitly set to use the Fiddler proxy), that you have enabled decryption of HTTPS traffic and that you have installed and trusted the root certificate. Additionally, some specific network configurations like VPN or security tools might also be causing side effects.
The above said we would need some more information about your specific network setup and about the application you are trying to monitor. Also is there any traffic being captured in your browsers, or is it a specific endpoint causing the issue?