Login to start a new topic
Answered

Unable to capture request

Hello,

Fiddler cannot run correctly on my mac. After I opened fiddler, I opened chrome to access the URL and it was not captured. My mac version is macOS Catalina10.15.7. I have closed other proxy applications before opening fiddler. But fiddler still cannot run correctly. 

Please help.


Best Answer

Hey  523410611 ,


This sounds like the reason why FE won't set the proxy - it lacks the administrative privileges. We logged this one as a bug, but meanwhile, you should be able to temporarily resolve the issue by doing the following on your side.


  1. Go to “System Preferences” > “Security & Privacy”
  2. Click the lock to make changes.
  3. Click on "Advanced…"
  4. Uncheck "Require an administrator password to access system-wide preferences."

(video reference)


Then, restart FE and enable the capturing.



As an alternative solution, you could manually set the FE proxy before starting to capture the requests. Use 127.0.0.1 for IP and  8866 for port (these are the defaults in FE).


2 people have this question

I think there is something wrong with the operation sequence you told me. If I set the agent manually first, it will lead to the failure to access the network, so I cannot log in FE. I changed the order of execution, first turned on FE, and then set the proxy manually.Hope these logs are helpful.

log
(6.31 KB)
log
(24.8 KB)

1 person likes this

Ihsan.gaozp could you try adding the following line in your .bashrc file (and then retrying the Fiddler Everywhere startup)


export BASH_SILENCE_DEPRECATION_WARNING=1

@Nick Iliev  but I'm using zsh as default terminal.

Hey guys,



To further investigate the case, you will need to install a custom Fiddler Everywhere build which will generate more verbose log files. If you have time please do the following:


1.Open this URL (NOTE: it is a new build) and download the .dmg file. Please note that in some cases Sharepoint does not show the actual file the first time when the URL is opened. If that happens on your side, please try opening it again and you should see the file.

2. Install the downloaded .dmg file. This is a special version prepared for this case - 1.1.0-ticket11326. You'll probably be asked to replace the existing application, you can select to do it.
3. Delete the ~/.fiddler directory.
4. Delete ~/Library/Application\ Support/Fiddler\ Everywhere directory
5. In Finder open the Applications directory.
6. Find the just installed version of Fiddler Everywhere and double-click it.
7. In the opened screen you should be asked to sign up, but there will be a button to sign in. Please use it and try to sign in with your credentials.
8. Wait a couple of minutes, for example 2-3. If the application is still in the loading screen, please close it.
9. Get the logs from ~/Library/Application\ Support/Fiddler\ Everywhere/Logs directory and send them to us for investigation.
10. Download the latest official version of the application from here.
11. Install the latest official version. This way you'll not be stuck with this custom version (as mentioned earlier this is a custom version without auto-update functionality in it).

Thanks a lot for your cooperation in the investigation of this issue.

I have reinstalled FE, but FE still cannot set my OS agent Settings. After checking, I found that FE could access the OS network Settings normally, but FE did not set the agent when I opened the capture. The following is the output command after opening the agent

image

Could you post the output for the web proxy (HTTPS) and the secure web proxy (HTTPS)? Those are actually the only two proxies that Fiddler Everywhere will set (when capturing is on).


networksetup -getwebproxy "Wi-Fi"
networksetup -getsecurewebproxy "Wi-Fi


Hey everyone,


We've prepared a new custom build for you, with the following changes applied in it:
1. Added more logs in several places to be sure which is the part of the code that hangs.
2. Added timeout of execution for the step that we think hangs. The timeout is set to 30 seconds. If it is reached, the operation will be canceled and the other operations should continue, i.e. you should be able to sign in.
3. Added a new log file for one of the packages that we think hangs.

So, can you please follow the steps below:
 

1.Open this URL (NOTE: it is a new build) and download the .dmg file. Please note that in some cases Sharepoint does not show the actual file the first time when the URL is opened. If that happens on your side, please try opening it again and you should see the file.

2. Install the downloaded .dmg file. This is a special version prepared for this case - 1.1.0-ticket11326. You'll probably be asked to replace the existing application, you can select to do it.
3. Delete the ~/.fiddler directory.
4. Delete ~/Library/Application\ Support/Fiddler\ Everywhere directory
5. In Finder open the Applications directory.
6. Find the just installed version of Fiddler Everywhere and double-click it.
7. In the opened screen you should be asked to sign up, but there will be a button to sign in. Please use it and try to sign in with your credentials.
8. Wait a couple of minutes, for example 2-3. If the application is still in the loading screen, please close it. If the application loads, please try to disable/enable capturing and see if it changes something.
9. Get the logs from ~/Library/Application\ Support/Fiddler\ Everywhere/Logs directory and send them to us for investigation. NOTE: There will be at least three files there, we'll need all of them.
10. Stop the application.
11. Delete the ~/.fiddler directory.
12. Delete ~/Library/Application\ Support/Fiddler\ Everywhere directory
13. Try to run it from a terminal, i.e. execute:
$ open /Applications/Fiddler\ Everywhere.app/
14. In the opened screen you should be asked to sign up, but there will be a button to sign in. Please use it and try to sign in with your credentials.
15. Wait a couple of minutes, for example 2-3. If the application is still in the loading screen, please close it. If the application loads, please try to disable/enable capturing and see if it changes something.
16. Get the logs from ~/Library/Application\ Support/Fiddler\ Everywhere/Logs directory and send them to us for investigation. NOTE: There will be at least three files there, we'll need all of them.
17. Download the latest official version of the application from here.
18. Install the latest official version. This way you'll not be stuck with this custom version (as mentioned earlier this is a custom version without auto-update functionality in it).


Thank you all in advance for your cooperation!

This is the result I output according to your request.

image


Fiddler Everywhere needs administrative rights to set the proxy settings on your OS (when capturing is ON the Fiddler proxy 127.0.01:8866 is set for web proxy and secure proxy). However, in your case, it looks like that your account has limited rights, and the proxy settings can't be set manually or via Fiddler (that is based on the inactive proxy settings in the OS screen you have previously shared). 


Could you let us know if you can manually change the proxy settings for the "Wi-Fi" connection.? If not, you need to contact your OS administrator and ask him to provide rights so that Fiddler Everywhere could change the proxy settings.

The account I used is the administrator account. If I manually set the agent to 127.0.0.1:8866 in the agent setting, FE can normally capture the request. I don't know what caused FE to fail to set up my agent.

Hello Everyone,

 

I am posting an updated link to the latest custom build. Notice that this build should be used only for troubleshooting the discussed issue while following the steps described above.

 

Link to the custom build

Hey,


Sorry to hear that you have trouble running Fiddler Everywhere on your macOS.


Can you please let us know if you were experiencing the issue with non-secure HTTP or with secure HTTPS traffic (or both)? Are you by chance using any third-party security tool, firewall, VPN? Also, you could post the Fiddler Everywhere logs. Refer to the following KB articles for more details on how to troubleshoot your case:


https://docs.telerik.com/fiddler-everywhere/knowledge-base/accessing-fiddler-logs


https://docs.telerik.com/fiddler-everywhere/knowledge-base/troubleshoot-mac-proxy-settings


https://docs.telerik.com/fiddler-everywhere/knowledge-base/troubleshoot-traffic-capturing

If you have a minute, do the following - set the proxy manually, start FE, start capturing, then stop capturing and lastly, send us the logs files (see how to obtain the Fiddler log files here). 

Hey there,


The order issue makes sense! 


Could you let us know if Fiddler Everywhere continues to work correctly once the proxy is set manually (FE started > proxy set manually > start capturing > stop capturing > close FE > start FE > start capturing)? Will appreciate it if you delete the Fiddler Everywhere logs before the above operations so that you could generate new clean log files. Additionally, please let us know how the request is made (what browser or application are you using to make the HTTPS requests) and if the used application has some proxy settings that need to be configured alongside Fiddler Everywhere. 

Login to start a new topic