Fiddler not capturing traffic from browsers

Question

I\'ve been using Fiddler for quite a while, but all of a sudden it no longer captures internet traffic. I\'m on Chrome 29 and Fiddler v4.4.5.1. I\'ve checked all filters a

Answer 1

Not sure if this is relevant but I had the same problem with Fiddler after the last update (v2.4.5.0). I turned all filters off but still wasn't picking up any traffic. When I unchecked Use Filters on the filters tab, however, all traffic was picked up as normal. I'm still trying to figure out how I can use filters when just checking Use Filters box causes all traffic to be blocked.

Answer 2

EDIT: I thought my issue was solved through the WinINET Options. Below are the steps that fixed my Chrome traffic finally being picked up in Fiddler:

From Fiddler -> Tools -> WinINET Options -> LAN settings -> Make sure Automatically detect settings is checked.

However, what I just found out later was that the PAC script was resetting these options everytime I fired up Fiddler. The real solution was goto Fiddler -> Tools -> Options -> Connections -> Uncheck Use PAC Script. This solved it for good. Below is a screenshot for reference:

Answer 3

1. Might be you have selected non browsers as an option
2. Select Web browsers instead of non browsers

Answer 4

For me i tried everything on here and eventually it boiled down to a corporate proxy that kept on resetting the INET Settings.

I worked my way down the list of suggestions but in the end turned out to be the proxy settings. I had hunch about it but i wanted to be thorogh about it before going to 'IT' and saying can i have local bindows proxy settings override please?

I asked for the proxy management software to be removed and then within a second fiddler started working. If you cannot override the proxy settings in Internet Properties then fiddler will never work.

Answer 5

Another possible issue is related to WCF client (this may also include other clients but i'm not sure). The client can be configured not to use the machine default proxy, which makes the client/application bypass Fiddler capture.

For further reading: What is the purpose of usedefaultwebproxy in WCF.

Answer 6

I encountered the same issue with https and solved it by checking the HTTPS Decryption

• Goto Fiddler Options -> HTTPS
• Check 'Decrypt HTTPS traffic'