Hi,
I use Fiddler a lot to debug an application, and Fiddler Core for my own application. Both have the problem that when I start capturing and decoding HTTPS traffic with the fiddler certificate that eventually (hours to days) my PC has no internet connection whatsoever. My browsers report that DNS lookups failed, Chrome sometimes says "ERR_NAME_RESOLUTION_FAILED", and so on. The only solution to restore connectivity is to stop capturing https, remove the certs, and restart the PC. There are also less severe cases when I only lose internet when I close Fiddler. All of this is bothersome for me and unacceptable for my app. Is there anything I'm doing wrong? I leave the default options in Fiddler except for the https capturing and decrypting. I use an auto-updated win 8 and auto-updated fiddler 4.4.9.2. I am on a home LAN behind a router/modem.
I use Fiddler a lot to debug an application, and Fiddler Core for my own application. Both have the problem that when I start capturing and decoding HTTPS traffic with the fiddler certificate that eventually (hours to days) my PC has no internet connection whatsoever. My browsers report that DNS lookups failed, Chrome sometimes says "ERR_NAME_RESOLUTION_FAILED", and so on. The only solution to restore connectivity is to stop capturing https, remove the certs, and restart the PC. There are also less severe cases when I only lose internet when I close Fiddler. All of this is bothersome for me and unacceptable for my app. Is there anything I'm doing wrong? I leave the default options in Fiddler except for the https capturing and decrypting. I use an auto-updated win 8 and auto-updated fiddler 4.4.9.2. I am on a home LAN behind a router/modem.
2 Answers, 1 is accepted
0
Hi, Matthias--
I run Fiddler 24/7 for weeks and have never seen any problem like the one you describe.
All of the errors you mention are errors that would be shown when the browser's DNS lookups fail; browsers do not use DNS when Fiddler or FiddlerCore are capturing their traffic, so your question is especially confusing.
Is there some reason you believe this is related to HTTPS-- does the problem not occur if you don't enable decryption, for instance?
In the failing scenario, if you go to a command line and type nslookup google.com what happens?
Regards,
Eric Lawrence
Telerik
I run Fiddler 24/7 for weeks and have never seen any problem like the one you describe.
All of the errors you mention are errors that would be shown when the browser's DNS lookups fail; browsers do not use DNS when Fiddler or FiddlerCore are capturing their traffic, so your question is especially confusing.
Is there some reason you believe this is related to HTTPS-- does the problem not occur if you don't enable decryption, for instance?
In the failing scenario, if you go to a command line and type nslookup google.com what happens?
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
Matthias
Top achievements
Rank 1
Rank 1
answered on 06 Sep 2014, 07:36 AM
The problem has never happened without Fiddler capturing HTTPS, but that may have been coincidence, because I also leave it running for a long time, so any problem that occurs would occur with Fiddler running. I don't know about Fiddler running without HTTPS, since I always need the HTTPS decryption. I will try to recreate the problem without HTTPS, and I will try to fix the problem when it occurs without disabling HTTPS decryption. Maybe the problem is with my ISP or router having issues at times, I will try to find out.