Simple as that: fiddler everywhere does not capture traffic to localhost, 172.0.0.1 AND when you insert your local address, it captures your request only to return that "

[Fiddler] DNS Lookup for "www.192.168.0.18" failed. System.Net.Internals.SocketExceptionFactory+ExtendedSocketException Device not configured

"...

MAC OSX, using safari.

Other address are captured as expected

I'm running on an Ubuntu 18.04 server. using VNC via gdm3 (gnome) display manager.

The first time I tried to run progress-telerik-fiddler.AppImage, it brought up a dialog asking if I wanted to integrate with VNC and install a desktop icon, to which I answered yes.

The window then closed, and each time I try to run progress-telerik-fiddler.AppImage again, nothing at all happens, as follows:

wxr-xr-x 1 root root 113958410 Mar 25 14:15 progress-telerik-fiddler.AppImage
root@cupertino:/nethome/osmolyar/fiddler#

There is no desktop icon, log, or anything.

tazik@mx-linux:/mnt/Software/Linux
$ ./progress-telerik-fiddler.AppImage --no-sandbox
License accepted
zenity, kdialog, Xdialog missing. Skipping /tmp/.mount_progrekwdZmY/AppRun.
14:44:47.550 › [Product information] Progress Telerik Fiddler 0.5.0
14:44:47.561 › [System information] Linux mx-linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux
14:44:47.698 › Initializing splash screen.
14:44:47.832 › Attempting to run server - 5 attempts left.
14:44:47.832 › Generating random port.
14:44:47.833 › Trying to start server at port [39169].
14:44:49.324 › Fetching .NET Core server status.
14:44:49.338 › Error occurred while fetching .NET Core server [39169] status. Error message: connect ECONNREFUSED 127.0.0.1:39169
14:44:49.338 › Attempting to run server - 4 attempts left.
14:44:49.338 › Generating random port.
14:44:49.338 › Trying to start server at port [14105].
14:44:50.065 › Fetching .NET Core server status.
14:44:50.071 › Error occurred while fetching .NET Core server [14105] status. Error message: connect ECONNREFUSED 127.0.0.1:14105
14:44:50.072 › Attempting to run server - 3 attempts left.
14:44:50.072 › Generating random port.
14:44:50.072 › Trying to start server at port [64355].
14:44:50.788 › Fetching .NET Core server status.
14:44:50.792 › Error occurred while fetching .NET Core server [64355] status. Error message: connect ECONNREFUSED 127.0.0.1:64355
14:44:50.792 › Attempting to run server - 2 attempts left.
14:44:50.792 › Generating random port.
14:44:50.792 › Trying to start server at port [4034].
14:44:51.504 › Fetching .NET Core server status.
14:44:51.509 › Error occurred while fetching .NET Core server [4034] status. Error message: connect ECONNREFUSED 127.0.0.1:4034
14:44:51.509 › Attempting to run server - 1 attempts left.
14:44:51.510 › Generating random port.
14:44:51.510 › Trying to start server at port [28542].
14:44:52.228 › Fetching .NET Core server status.
14:44:52.233 › Error occurred while fetching .NET Core server [28542] status. Error message: connect ECONNREFUSED 127.0.0.1:28542
14:44:52.233 › Attempting to run server - 0 attempts left.
14:44:52.234 › Maximum number of attempts reached - quitting application.
14:44:52.260 › Generating random port.
14:44:52.261 › Trying to start server at port [25311].
tazik@mx-linux:/mnt/Software/Linux
 

Hi all,
I tried to start app but every time nothing happens except short appearing a splash screen. Bellow detail from terminal:

***************

Add the ability to capture traffic, filter traffic in real time, intercept & modify sessions, decrypt https traffic, etc.

Im using MacOS Sierra 10.12.5

2 BIG Issues are present.

First of all, I don't have an INTERNET connection any more after closing FIDDLER it has to be always running!

Second issue Fiddler is working properly ONLY on the first Start. If  closing it and opening it again it's not working at all.

FIX this ASAP

very very critical

In Fiddler (and in applications such as Wireshark) it's easy to collapse / switch between different protocols, headers and such.

In the Fiddler everywhere version - you get the entire request/response as a single text block.

It would be great to switch between protocols / collapse the parts you care less about and in general have better controls.

I'm so excited to see you working on a cross-platform version.  Your MacOs version was never really usable.  Everywhere is already better than the Mac version was!

Edit and resend requests,  Compose from scratch and send requests.

I mainly use Fiddler for WebApi testing, debugging, monitoring.  The ability to capture, modify, and resend a request is a key feature for me.

Mac/Linux

I would like to be able to configure the following values via command line in the Mac version of Fiddler Everywhere:

In Preferences:

• Decrypt HTTPS traffic (under HTTPS)
• Fiddler listens on port: #### (under Connections)
• Act as system proxy on startup (under Connections)
• Manual Proxy configuration (under Gateway)

The best way that I've seen this implemented is in Chrome.

Chrome's settings are by default stored in a JSON file, but a Mac administrator can configure settings using MacOS's built-in preference system (either via the command `defaults write` or using a config profile) which will then enforce the settings.

In the meantime, if there's a text file I can edit, I'd love to do that.

When I toggle the 'Live Traffic (Capturing)', mac prompts for a password. When this prompt is canceled by the user (no password entered) the toggle incorrectly toggles to off/on.

Steps to Reproduce:

1. Fiddler Everywhere open on a Mac

2. Toggle 'Live Traffic (Capturing)'

3. Select 'Cancel'

4. Notice Toggle changes state and the state of the Capturing does not change. 

Expected Result: The 'Live Traffic (Capturing)' toggle does not change state if the mac users permissions are not accepted. 

Observed Result: The 'Live Traffic (Capturing)' toggle changes state if the mac users permissions are not accepted. 

Having used the original Fiddles for almost a decade. The new one looks great, but the UI scaling is way too big and spacious for actual production work.

We may have hundreds of requests in one test case and it's important that we see as many requests as possible on one screen so that we can get the whole picture how a service works (for example when reverse engineering something that's badly documented).

With the new UI it's only possible to see few dozen requests, so some kind of UI scaling is required. Also the inspector windows use way too much vertical space. It's really hard to see what's happening in a large request/response.

In my opinion the usability and productivity are more important than how sleek or modern the UI looks. Please prioritize the usability of the UI. Until then, I will be enjoying the classic Fiddler :)

Thanks.

Operating System: macOs Catalina 10.15.4

Step by step instructions on how to reproduce the problem:

1. Connect to VPN (mine is Cisco AnyConnect).
2. Open fiddler capture traffic.

You can also do the following to reproduce the problem:

1. Open fiddler capture traffic.
2. Connect to VPN (mine is Cisco AnyConnect).

Use case: I work remotely and connect to a VPN. In comparison, Charles Proxy can capture traffic when VPN is on. The comparison was to point out traffic is possible to be captured on VPN to counter any arguments.

While inspecting requests where Content-Length > 3000, only 3000 characters of the request body gets displayed in both Raw and Text views. When I copy the whole contents of the selectable area (CMD + A, CMD + C) and paste it into a text editor, it seems like there is a 'View full request...' text somewhere which does not show up. I remember this button from previous versions. 

OS : macOS Mojave Version 10.14.6

A sample HTML with dummy form to reproduce the bug and recorded session is attached.