As soon as we start Fiddler Everywhere for profiling we got the following error in our application whenever a gRPC-call is executed:

Connection id "0HMT23GS5CF6U", Request id "0HMT23GS5CF6U:00000001": An unhandled exception was thrown by the application.

Error: Grpc.Core.RpcException: Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: Unable to get subchannel from HttpRequestMessage. (127.0.0.1:8866) InvalidOperationException: Unable to get subchannel from HttpRequestMessage.", DebugException="System.Net.Http.HttpRequestException: Unable to get subchannel from HttpRequestMessage. (127.0.0.1:8866)") ---> System.Net.Http.HttpRequestException: Unable to get subchannel from HttpRequestMessage. (127.0.0.1:8866) ---> System.InvalidOperationException: Unable to get subchannel from HttpRequestMessage. at Grpc.Net.Client.Balancer.Internal.BalancerHttpHandler.OnConnect(SocketsHttpConnectionContext context, CancellationToken cancellationToken) at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)

Any idea how to fix this?

 

br

I also tested using the built in browser launcher from Fiddler Everywhere to https://libwebsockets.org/testserver/

and I'm not seeing any Websocket tabs anywhere or any of the ws traffic. There's a lot of HTTP.

Additionally, in our application the http(s) connections use the Upgrade mechanism to upgrade to a ws(s) connection but the listening port on our service is not being used in whatever the fiddler proxy thing is doing. I just see attempts to go to port 80. Is this something we configure in Fiddler Everywhere?

Hi
I am a software tester.
After installing the latest version of fiddler(4.3.2) I am unable to inspect the traffic from iOS app which I am testing. I spend a lot of time to understand the issue and finally I found it is only happening in latest versions.
The app is getting stuck and API requests are not being shown in the fiddler. Not sure but I think it has to do with TLS 1.3.
Working version-4.0.1
When I install this version(4.0.1) it gets updated to latest version automatically when I close and relaunch the fiddler.
How to resolve this issue please?

When I click Accept User License Agreement, I get an error, which prevents me from using Fiddler EveryWhere

Hi!

Is it possible to configure Fiddler Everywhere to save (I only need headers) the traffic log at certain times? A script would be great too if there is no GUI option.

Thanks in advance!

I have tried all the methods on this website, but I am unable to intercept HTTPS. Please help me.

 

url ：https://visa.vfsglobal.com/chn/zh/pol/    

Attempting to refresh using F5 will prompt: Sorry, you have been blocked

我尝试了所有方法，但无法解密他的HTTPS。请帮助我。

网址：https://visa.vfsglobal.com/chn/zh/pol/

请尝试使用 F5 刷新页面，它会提示：对不起，您已被阻止。

谢谢。

I manually added the fiddler cert to the trust certificate folder, but fiddler is still showing a red dot next to trust root certificates.

when i click on the button to have the cert added, it fails.  I don't know what do do next.

 

I am on windows 11

In Fiddler Everywhere on Mac I try creating a redirect to catch requests sent to https://my.url.here/this/that/0.0.112/filename and serve some locally stored files instead. This is for a development environment on a project. I have created the following rule:

Conditions:
URL Contains: https://my.url.here/this/that/

Rules:
Update Url
Regular expression:
/https:\/\/my.url.here\/this\/that\/[0-9\.]+\/(.+)
/Users/firtname.lastname/Projects/projectname/dist/$1

The Condition is triggered because I also have a rule to color the requests and I can see that the requests are colored as I expect it. The regex Rule is probably not executed because the files are still served from https://my.url.here/this/that/... instead of the locally stored files.

Could you please advise what I am doing wrong with my regex or anything else?

Thank you.

Hi,

On June 13, around 19:00 UTC, the Fiddler Everywhere team discovered an issue with the login backend, which prevented some of our users from logging in and using the app. The issue was resolved shortly before 21:00 UTC and the team is now monitoring the service health. 

If you have experienced "Gateway Timeout" errors while trying to login, please try again now.

If you have purchased a license during that time, but your account does not show it now, please contact us to resolve this.

Please accept our apologies for the inconvenience.