Just downloaded and tried to use Fiddler Everywhere for Mac osx - 

MacBook Pro (15-inch, 2017)

16 GB 2133 MHz LPDDR3

Catalina - 10.15.7 (19H1922)

 

When I launch Fiddler Everywhere 3.3.1

Nothing happens it tries to start, says loading in the prompt then crashes.

I am trying to do the trial

 

Any advice?

When I run fiddler with a proxy for the BlueStacks Android emulator (on Windows), many of the results are listed as "Tunnel to" a random IP address, with no headers and no information on the data sent. Clicking on one reveals "A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below." but nothing else that I can decipher.

I have HTTPS capture and decrypt on, and it works for a few API calls from this app, but the majority are shown as the IP addresses explained above.

Am I doing something wrong? How can I fix it so that I can see information on these.

Hi guys,

I'm using different proxies for each browser, let's say 5 different proxies/IPs.

The question is: How to make the fiddler classic capture the traffic (requests/responses) from all the browsers? It means that it should read the traffic from 5 proxies at the same time.

Having updated Windows 10 to 11, fiddler will no longer launch. 

I've tried uninstalling/reinstalling, but see the same effect.

The application event log shows the following pair of entries each time:

Faulting application name: Fiddler.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000079b2a6dc
Faulting process ID: 0x3f6c
Faulting application start time: 0x01d8a0fe70d97aab
Faulting application path: C:\Users\XXXXX\AppData\Local\Programs\Fiddler\Fiddler.exe
Faulting module path: unknown
Report ID: d9f21a10-a4e4-4806-8ccd-6d4f797efb48
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: Fiddler.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000002cf8a6dc
Faulting process ID: 0x4474
Faulting application start time: 0x01d8a0fe70d8e0fc
Faulting application path: C:\Users\XXXXX\AppData\Local\Programs\Fiddler\Fiddler.exe
Faulting module path: unknown
Report ID: 1556ffc4-1807-4032-b399-33a49dc42611
Faulting package full name: 
Faulting package-relative application ID: 

 

Bright ideas?

i know how to retry a request on normal 500 error or when it give error in OnReturningError chain

but the problem is the error with HTTP/1.1 0 FIDDLER GENERATED - RESPONSE DATA WAS MISSING and response code 0 wont retry what chain exactly handle this error ?

 

How to disable the echo service?

After I download the cer from the http://fiddlerip:port/ , I do not need the echo service anymore. And for security, I need just keep proxy func, and shutdown the echo service.

After search whole google, can not find clue.

Anyone can help?

Thanks

I have a website that sent an error message: "err_connection_aborted" when I connect to it using HTTPS.

When I have Fiddler active it works perfectly, so I'm not really able to debug the issue.

I've been fighting this error for several days... should be very easy, it's just a webpage under HTTPS. It works OK in HTTP, but something goes wrong with HTTPS.

 

Thanks!

I am a new Fiddler classic user on Windows 10.  I can easily monitor http(s) requests of my browsers such as Chrome or Microsoft Edge. However, no http(s) requests are seen from my Application "Ubuntu on Windows". I have checked it (exemted) in WinConfig toolbar. What could be the problem here. Thanks in advance!

I ran a trace from a handheld device to a server in a data center. In short, the trace reads:

- ClientConnected: 12:44:55

- ServerConnected: 12:50:39

- ServerBeginResponse: 12:50:51

Does this mean that the Server spent 12 seconds data processing before responding?

 

 

 

this is a feature proposal. With comments made by user, we can easily trace back the session after saving lots of sessions.