Hello,
I too am having issues with Fiddler, I've been using it for years as well and have downloaded the latest version (although the issue showed up earlier today in the previous version I had installed). I can't say when this started - other than most probably sometime in the last week, I tend to use Fiddler a lot but just noticed it today.
The symptoms are as follows...
If I turn capture on, all HTTP requests fail. If I try in Chrome, I can view more error details and see ERR_CONNECTION_RESET at the bottom of the screen.
I have "Use Filters" unchecked.
I have clicked "Troubleshoot Filters" but my requests are not showing up in Fiddler.
I have tried both http://localhost:8888 and http://ipv4.fiddler:8888 when Fiddler is capturing and I receive nothing in Fiddler, and an ERR_CONNECTION_RESET message when I drill down into the error shown by Chrome.
I have checked proxy information, it is being set to 127.0.0.1:8888 as expected for both Http and Https when capturing. When not capturing the details in WinInet are blank (no proxy server).
I usually see a raft of logs when I have Fiddler enabled from my Win8 apps, now it's all completely clear - which leads me to believe that it's a system wide issue. I've reset the Win8 config but that made no difference.
I have tried Chrome, IE and FF but all exhibit the same behaviour.
The version I am running is v4.4.8.4, 10th June 2014.
Looking at my Firewall (Windows Firewall only) I see "FiddlerProxy" enabled with both Private and Public checked.
When running a new instance I see the following in the log...
14:24:45:8803 Fiddler Running...
14:24:45:9143 Windows 8+ AppContainer isolation feature detected.
I am on Windows 8.1.
Any suggestions you have will be greatly appreciated!
Cheers,
Morgan
I too am having issues with Fiddler, I've been using it for years as well and have downloaded the latest version (although the issue showed up earlier today in the previous version I had installed). I can't say when this started - other than most probably sometime in the last week, I tend to use Fiddler a lot but just noticed it today.
The symptoms are as follows...
If I turn capture on, all HTTP requests fail. If I try in Chrome, I can view more error details and see ERR_CONNECTION_RESET at the bottom of the screen.
I have "Use Filters" unchecked.
I have clicked "Troubleshoot Filters" but my requests are not showing up in Fiddler.
I have tried both http://localhost:8888 and http://ipv4.fiddler:8888 when Fiddler is capturing and I receive nothing in Fiddler, and an ERR_CONNECTION_RESET message when I drill down into the error shown by Chrome.
I have checked proxy information, it is being set to 127.0.0.1:8888 as expected for both Http and Https when capturing. When not capturing the details in WinInet are blank (no proxy server).
I usually see a raft of logs when I have Fiddler enabled from my Win8 apps, now it's all completely clear - which leads me to believe that it's a system wide issue. I've reset the Win8 config but that made no difference.
I have tried Chrome, IE and FF but all exhibit the same behaviour.
The version I am running is v4.4.8.4, 10th June 2014.
Looking at my Firewall (Windows Firewall only) I see "FiddlerProxy" enabled with both Private and Public checked.
When running a new instance I see the following in the log...
14:24:45:8803 Fiddler Running...
14:24:45:9143 Windows 8+ AppContainer isolation feature detected.
I am on Windows 8.1.
Any suggestions you have will be greatly appreciated!
Cheers,
Morgan
3 Answers, 1 is accepted
0
Hello, Morgan--
I don't know what "me too" means, but you've provided a few details that may be useful.
The symptoms described indicate that either you have another firewall installed and blocking Fiddler, or some software or configuration change has occurred that is breaking your network stack such that it cannot reach http://127.0.0.1:8888.
You might try running Fiddler on a different port (Tools > Fiddler Options > Connections) to see whether that impacts the issue.
Regards,
Eric Lawrence
Telerik
I don't know what "me too" means, but you've provided a few details that may be useful.
The symptoms described indicate that either you have another firewall installed and blocking Fiddler, or some software or configuration change has occurred that is breaking your network stack such that it cannot reach http://127.0.0.1:8888.
You might try running Fiddler on a different port (Tools > Fiddler Options > Connections) to see whether that impacts the issue.
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.
0
Morgan
Top achievements
Rank 1
Rank 1
answered on 30 Jun 2014, 03:00 PM
Eric,
I put "me too" to distinguish this from another thread with the same name.
I've just tried changing ports to 9999 and no change, it's doing (or rather not doing) exactly the same as before. I have Wireshark installed (not that I know how to use it properly) and can help out debugging if you have any further suggestions.
Cheers,
Morgan
I put "me too" to distinguish this from another thread with the same name.
I've just tried changing ports to 9999 and no change, it's doing (or rather not doing) exactly the same as before. I have Wireshark installed (not that I know how to use it properly) and can help out debugging if you have any further suggestions.
Cheers,
Morgan
0
Hi, Morgan
Unfortunately, I don't think Wireshark can see traffic that doesn't leave your PC, and since Fiddler runs locally it probably won't help to use Wireshark.
From a command prompt, you can type netstat -a -o to verify that Fiddler is properly listening on 127.0.0.1:9999.
From a browser, you might try visiting http://yourPCName:9999/ and verify that it doesn't load anything.
You might look in Add/Remove Programs for any recently installed software that might be interfering with your network stack.
Regards,
Eric Lawrence
Telerik
Unfortunately, I don't think Wireshark can see traffic that doesn't leave your PC, and since Fiddler runs locally it probably won't help to use Wireshark.
From a command prompt, you can type netstat -a -o to verify that Fiddler is properly listening on 127.0.0.1:9999.
From a browser, you might try visiting http://yourPCName:9999/ and verify that it doesn't load anything.
You might look in Add/Remove Programs for any recently installed software that might be interfering with your network stack.
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.