Yes I have tried resetting IE settings
Yes I have disabled and re-enabled IE
Yes I have tried the following steps:
1: Use Help > Troubleshoot Filters to make sure the traffic isn't getting hidden unexpectedly. --Nothing hidden
2: Look in the Log tab to see if there's a note about Chrome Group Policy hardcoding the proxy. --Recently set Chrome Policy to try and fix the issue. Not problematic
3: Update your question to mention whether other browsers' traffic is captured. --Nothing is captured except for Echo Service
4: Visit http://localhost.fiddler:8888/ in Chrome; What if anything do you see? --Echo Service
5: Visit http://127.0.0.1:8888/ in Chrome; What if anything do you see? --Echo Service
I have also tried to manually modify the registry settings. The result was Fiddler overriding them. I have tried process monitor, nothing is being captured at all.
After setting the Chrome Policy, it works, for Chrome anyways. I have disabled EVERY Chrome expansion. Nothing. I have also deleted Registry Keys, nothing.
I have crashed Windows trying to fix this, believe me I went in-depth. I have uninstalled the following as well to try:
1: Evolve VPN
2: Teamviewer VPN
3: Wireshark
4: WinPCap
5: Fiddler (Reinstalled)
6: CommView
With the exception of Fiddler, I have reinstalled nothing above. I do have Hamachi VPN installed, but I know it works for that. Note I am having the same exact issue on another laptop, meaning it is not entirely unique. The registry override ONLY occurs when refreshing Fiddler after registry change. I am ready to post any files I need.
11 Answers, 1 is accepted
Rank 1
I have used Fiddler before, and I loved it. I need more like it. But with the Chrome Policy I should be able to do what I need to do, for now. Yes, I am a programmer, I am using Fiddler to make it easier for my to determine how to do what I need to do, instead of hours of research.
This: 4: Visit http://localhost.fiddler:8888/ in Chrome; What if anything do you see? --Echo Service
Means that your browser is sending traffic correctly to the proxy (otherwise, localhost.fiddler would be shown as a DNS error in your browser).
If your problem isn't with Chrome, follow the steps in the browser you're having trouble with.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Rank 1
When I edit the registry files, it seems like Fiddler is preventing it from enabling. Fiddler thinks it is running and does receive things sent to 8888 but does not actually cause anything to be routed that direction. Basically I listens but doesn't proxy I suppose. And because of this it only works for chrome. And no IE is not picked up.
Rank 1
#4 Is now a DNS issue Liekly had policy active for chrome at time
IE does not get picked up
It does listen on port 8888
Doesn't proxy so I cannot use it outside chrome.
Rank 1
#4 Is now a DNS issue Likely had policy active for chrome at time
IE does not get picked up
It does listen on port 8888
Doesn't proxy so I cannot use it outside chrome.
If Fiddler is unable to set the system proxy (e.g. because there's security software that prevents it, or other software that immediately overwrites its changes) then traffic will not be sent to Fiddler, but the "Echo" page will remain available at http://127.0.0.1. You can see what proxy is currently configured by choosing Tools > WinINET Options > LAN Settings inside Fiddler or Tools > Internet Options > Connections > LAN Settings inside IE.
Another case occurs when the system's proxy setting logic is broken and the settings cannot be changed. To check for that, without Fiddler running, go to the LAN Settings and configure a bogus proxy (e.g. http://bazinga on port 9999). Click OK on the dialogs and then reopen them. If the settings weren't preserved, then the system APIs are broken. This could be a result of a bug in the OS, or VPN software, or malware, or any host of other similar issues.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Rank 1
Rank 1
A Process Monitor log, filtered to the ProxyServer registry key would be useful to see what exactly is happening. Bugs in the proxy settings API have been reported to the WinINET team at Microsoft, but as no one has a reliable repro, I don't think they've made any progress in finding the root cause. You might try using IE's Tools > Internet Options > Advanced > Reset... but there's no particular reason to believe that this will work.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
Rank 1
And from what I can tell ProcessMonitor is picking not a thing up, and strangly not even Fiddler, although I, as said before, believe it may be causing it. Regardless, nothing is determined. Internet Options don't work of course but when modifiying the registry settings for manual changing, Fiddler appears to override it, regardless of ProcessMonitor's lack of ability to detect crap.
Rank 1