Fiddler Everywhere is failing with below error if HTTPS traffic is enabled.
Did the below:
1) Trusted Fiddler root certificate on my PC and mobile
2) Configured manual proxy over my Wi Fi to route network traffic from my mobile application to fiddler on desktop
3) Enabled capture HTTPS traffic
4) The app I am trying to debug network traffic is blink for home.
But all the requests are failing with the below error in the image. please help.
Hello,
I've use Fiddler Everywhere on my mac for several months. Today I updated to the last version 1.5.1 and localhost traffic is not showing anymore.
Any ideas?
Thanks
Erick
I installed Fiddler Web Debugger, and I am trying to configure it to monitor the HTTP calls from Adobe Reader/Acrobat DC. I have Dynamic PDF forms that will invoke URLs using JavaScript under Acrobat. I appreciate your guiding me to configure Fiddler to debug such HTTP calls. Mind you that I managed to debug the calls from IE, and now I want to debug the same from Adobe Acrobat DC.
Tarek
Hi,
I need to capture SharePoint API calls, but Fiddler is not capturing anything. I suppose it is due to a proxy but don't know how to set up.
Can somebody help me?
Hey all,
I got the following error while I'm importing the following pcap in Fiddler which I earlier convert from .saz to .pcap. Can anyone please tell how can I fix this error
Hi. I am working with a web page that makes requests to an API and is returning a Json.
When I use the Fiddler it only shows me Tunnel to xxxxx: 443.
In the following elements, neither the request information nor the response with the Json appear. Is there any way to see it?
I run Fiddler on ubuntu 19.10
Startup log:
zhaozhe@zhaozhe-MRC-WX0:~/soft$ ./progress-telerik-fiddler.AppImage
16:57:14.645 › [Product information] Progress Telerik Fiddler 0.5.0
16:57:14.654 › [System information] Linux zhaozhe-MRC-WX0 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
16:57:14.770 › Initializing splash screen.
16:57:14.886 › Attempting to run server - 5 attempts left.
16:57:14.886 › Generating random port.
16:57:14.887 › Trying to start server at port [42420].
16:57:16.046 › Fetching .NET Core server status.
16:57:16.120 › Error occurred while fetching .NET Core server [42420] status. Error message: connect ECONNREFUSED 127.0.0.1:42420
16:57:16.120 › Attempting to run server - 4 attempts left.
16:57:16.120 › Generating random port.
16:57:16.120 › Trying to start server at port [39650].
16:57:16.540 › Fetching .NET Core server status.
16:57:16.626 › Error occurred while fetching .NET Core server [39650] status. Error message: connect ECONNREFUSED 127.0.0.1:39650
16:57:16.626 › Attempting to run server - 3 attempts left.
16:57:16.627 › Generating random port.
16:57:16.627 › Trying to start server at port [26748].
16:57:17.066 › Fetching .NET Core server status.
16:57:17.150 › Error occurred while fetching .NET Core server [26748] status. Error message: connect ECONNREFUSED 127.0.0.1:26748
16:57:17.150 › Attempting to run server - 2 attempts left.
16:57:17.150 › Generating random port.
16:57:17.150 › Trying to start server at port [12887].
16:57:17.575 › Fetching .NET Core server status.
16:57:17.648 › Error occurred while fetching .NET Core server [12887] status. Error message: connect ECONNREFUSED 127.0.0.1:12887
16:57:17.648 › Attempting to run server - 1 attempts left.
16:57:17.648 › Generating random port.
16:57:17.648 › Trying to start server at port [34621].
16:57:18.067 › Fetching .NET Core server status.
16:57:18.140 › Error occurred while fetching .NET Core server [34621] status. Error message: connect ECONNREFUSED 127.0.0.1:34621
16:57:18.140 › Attempting to run server - 0 attempts left.
16:57:18.140 › Maximum number of attempts reached - quitting application.
16:57:18.156 › Generating random port.
16:57:18.156 › Trying to start server at port [58068].