Hi John,

Fiddler Everywhere needs direct internet access with or without a VPN connection. If there is a VPN connection, then Fiddler must be started first (so that it could set the OS proxy settings), and after the VPN is created, it shouldn't modify the proxy settings. Here is a basic solution that works for Cisco VPN client alongside Fiddler Everywhere.

If you are unable to use the provided workaround then please let us know what is the VPN tool used on your side, and also any network-specific related to it and to your network setup.

Regards,
Nick Iliev
Progress Telerik

Hi,

The proxy auto discovery state is something we need in order to run the Fiddler Everywhere session capturing on macOS. If it fails on your machine then we are not going to be able to get and set proxy settings. I have one more suggestion - try renaming the W-Fi connection name and then try to run Fiddler and capture traffic. To rename the connection, go to System Preferences > Network, then select the Wi-Fi connection, click the cog wheel at the bottom of the connections list and select "Rename Service...". Chose a new name - e.g. "Wi-Fi-1" (without the quotes) and click "Rename". Finally, click the "Apply" button at the bottom right of the network settings window to apply the change. 

After that you can try starting Fiddler Everywhere and capturing again. If it does not work, check the output of the networksetup commands with the new name:

networksetup -getproxyautodiscovery "Wi-Fi-1"

networksetup -getautoproxyurl "Wi-Fi-1"

Regards,
Lini
Progress Telerik

Hello,

It seems the problem in your case is in the command that we use to get the proxy auto discovery settings:

networksetup -getproxyautodiscovery "Wi-Fi"

Can you try executing only this command in a terminal (no sudo is needed) and see if it fails again? You can also try to remove the quotes from the adapter name (Wi-Fi instead of "Wi-Fi") to see if it makes any difference. I am sure that you already did this, but please also try the command after restarting the machine.

Regards,
Lini
Progress Telerik

Hey John,

It looks like, in your case, there is something that is preventing Fiddler Everywhere from setting the proxy settings for the Wi-FI adapter.

Could you please execute the following commands manually and send us with the output:

networksetup -getproxyautodiscovery "Wi-Fi"
networksetup -getautoproxyurl "Wi-Fi"
networksetup -getproxybypassdomains "Wi-Fi"
networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi"
networksetup -getftpproxy "Wi-Fi"
networksetup -getsocksfirewallproxy "Wi-Fi"

The above commands depend on your active network adapter being the "Wi-Fi" one (as in the screenshots). If that is not the case (or the commands are failing due to a non-existent adapter), you could run the following script and send us the output (this script aims to get the name of the active network adapter).

services=$(networksetup -listnetworkserviceorder | sed '1d;s/^([^)]*) \(.*\)$/\1FIDDLER_SEPARATOR/g;s/^.*Device: \([^)]*\))/\1/g;/^$/d' | sed 'N;s/\n//')

while read line; do
    sname=$(echo $line | awk -F  "FIDDLER_SEPARATOR" '{print $1}')
    sdev=$(echo $line | awk -F  "FIDDLER_SEPARATOR" '{print $2}')
    if [ -n "$sdev" ]; then
        ifconfig $sdev 2>/dev/null | grep 'status: active' > /dev/null 2>&1
        rc="$?"
        if [ "$rc" -eq 0 ]; then
            currentservice="$sname"
            echo "$currentservice"
            break
        fi
    fi
done <<< "$(echo "$services")"

if ! [ -n "$currentservice" ]; then
    >&2 echo "Could not find current service"
    exit 1
fi

To run the script create a file with .sh extension and execute it in your terminal. For example, create test.sh, copy/paste the script, and then run the following:

sh <path-to-file>/test.sh

Regards,
Nick Iliev
Progress Telerik

He John Doe,

It looks like that, in your case, Fiddler Everywhere is not able to set the proper proxy settings. Could you please provide the following information so we could investigate further:

- Provide information about your active network interfaces. A screenshot of the OS Network Preferences window will help here.

- Output from the following command (from your terminal)

networksetup -listnetworkserviceorder

Regards,
Nick Iliev
Progress Telerik

Hello Steve,

Thanks for trying Fiddler Everywhere and for your feedback.

Regarding the issue with capturing not working can you please share more details so we could try to reproduce and fix the issue (if such is present). We need the following information:

- Information about your OS (version and build number).

- Let us know if there are 3rd party tools that are monitoring the network traffic (like firewalls, antivirus, or corporate security tools).

- Are you trying to capture traffic from a specific app/browser?

- Post the Fiddler logs (see my previous post in this thread for the Mac location) 

- Provide information about your proxy settings before and after capturing is turned on.

Regarding the version information

The version of the currently installed client is available during the client loading screen. The team will introduce an About functionality in one of the upcoming versions.

Regarding the issue with FE window being fully maximized

This is a known issue which the team acknowledged and is going to discuss on the upcoming planning meetings. Providing more information about your OS will help us a lot.

Regards,
Nick Iliev
Progress Telerik

Hi Sean-Michael,

We made extensive tests on MacOS Catalina but we were not able to reproduce the issue. Try completely resetting your Fiddler client (make a fresh reinstall) and also if possible send us the logs (after Fiddler has started). The logs on MacOS are located in:

~/Library/Application Support/Fiddler Everywhere/Logs

Regards,
Nick Iliev
Progress Telerik

Hello Sean,

Can you give an example for the external source which you are not able to capture - is it a web site that is not being captured or a 3rd-party application? If possible share URLs that are causing the issue.

Regards,
Nick Iliev
Progress Telerik

Hello Sean-Michael,

I am sorry for the confusion - the Fiddler 0.11 was just released yesterday so now you should be able to download and install the latest version.

Regards,
Nick Iliev
Progress Telerik

Hi Sean-Michael,

Thank you for using Fiddler Everywhere and for your feedback. Please try to update to the latest version of FE which of this very moment is 0.11.0 and let us know if the issue is still reproducible. If you are still experiencing the problem let us know if your FE client able to capture any traffic (for example non-secure HTTP from the Composer) and is your local setup using a VPN or corporate proxy?

Regards,
Nick Iliev
Progress Telerik