Fiddler doesn't capture traffic from IE

2 posts, 0 answers
  1. Jeff
    Jeff avatar
    1 posts
    Member since:
    May 2015

    Posted 28 May 2015 Link to this post

    I can see traffic from Chrome and Firefox just fine, but I get nothing from IE.

    It was previously working, a month or so ago, on IE10. I've tried re-installing Fiddler and IE10 (not at the same time).

    It worked while I was on IE8 but I don't want to use IE8.

    It didn't work on IE9, 10, or 11 today.

    I've tried starting Fiddler as admin / elevated.

    When I load the URI http://ipv4.fiddler:8888/ in firefox I see "Fiddler Echo Service..."

    When I load the same URI in IE I get "this page can not be displayed..."

    I can get it to work briefly by manually setting winINET proxy to, (and when this setting is in place http://ipv4.fiddler:8888/ works too) but if I touch the "capture" button in Fiddler at all (as if to enable or disable, either way) it stops capturing and doesn't restart until I manually re-enter the winINET proxy setting.

    This would be semi-OK but I need to chain to another upstream local proxy and as soon as I enable this Fiddler stops capturing again. I should note I use the same setup with the two proxy apps on another machine with no problem.

     I'm guessing *something* installed on this machine is preventing Fiddler from editing my winINET proxy setting, but I don't know what it could be. AFAIK I have all the same software on the other machine which is working nicely. Can you maybe suggest how I could go about tracking down the offending bit of software, if there is one?



  2. Eric Lawrence
    Eric Lawrence avatar
    832 posts

    Posted 29 May 2015 Link to this post

    Hi, Jeff--

    I'm not really sure what you mean when you talk about chaining to an upstream proxy? That proxy should be configured in IE before you start Fiddler, and you shouldn't manually touch proxy settings after that.

    What is a "two proxy app"?

    You can use SysInternal's Process Monitor to watch writes to the ProxyServer registry key to see which processes touch that key, but unless Fiddler is showing the yellow "Someone changed your proxy settings" notification, this probably won't reveal anything.

    Eric Lawrence
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top