Geek Answers Handbook

Proxying HTTPS traffic through Fiddler fails for remote clients?

The violinist started on one machine, included remote connections and HTTP. When I try to open IE browser on a remote computer (after manually setting proxy server settings) and try to go to https://www.gmail.com , I get a normal warning. When I try to "Continue to the website" I get the message "Certificate error: navigation failed."

Everything works fine when Fiddler and the browser work on the same computer.

Any help would be appreciated.

+6
source share
3 answers

You must configure the client machine to trust the Fiddler server certificate.

From the reference :

Q: Can Fiddler decrypt HTTPS traffic from another computer?

A: Yes, if you configured Fiddler to proxy traffic from a second computer or device, you can decrypt this traffic with two caveats:

  • If Fiddler was previously launched on the client computer in HTTPS decryption mode, all attempts to visit HTTPS pages protected by another computer version of Fiddler will fail with an undefined certificate error. To resolve this issue, delete the old Fiddler root certificate, which is located in the client’s trusted root server repository , using certmgr.msc. (An inappropriate root certificate causes a problem, as each instance of Fiddler generates its own unique root).

  • If you want the client computer to trust the Fiddler certificate, you will have to copy or download the Fiddler Root certificate to the client computer and manually install it in the store of trusted root certification authorities. You can download the Fiddler Root certificate by visiting the URL:

    http: //hostname.of.FiddlerMachine: 8888 / FiddlerRoot.cer

+12
source

If you have used Fiddler for a long time , especially if you use it through updates , you may find that Fiddler will not capture traffic no matter what you do for any browser, even if you click Trust Root Certificate until you are blue in face.

Trust Root Cert is usually the answer, but not when Fiddler filled your Cert store with bad certificates.

I experienced the message There is a problem connecting securely to this website. in IE and Chrome abandoned the ghost Your connection is not private

However, a very simple solution is to let Fiddler clear all of its old certificates from your machine and start a new one. Do this by clicking Reset All Certificates .

enter image description here

This will remove all old Fiddler certificates and create a new master interception certificate.

Note: this will not delete any other certificates, only Fiddler certificates.

This worked for me in two separate instances, without the need for a reboot.

+4
source

I would like to share with you a question and a resolution that works for me. I used the fiddler version - v4.6.3.50306, and suddenly it was HAPPY Https traffic and it shows an error in the Fiddler Inspector tab, as shown below:

Error Description -:

"The https handshake on server-xxxx.com failed. System.Security.Cryptography.CryptographyException. The specified network password is incorrect.

I am doing below things to solve the problem.

Reset all certificates under Tools → Fiddler Option → Https → Action Button → Reset entire certificate But this does not work.

Then after 3 disappointing days below the things RESOLVED by my problem -: :)

  • Open registry
  • search all entries with the words "fiddler" and "eric" also
  • Delete all registry files
  • Restart machine
  • Install fiddler again using admin prvilege
  • Restart machine
  • Now it begins to capture Https traffic, as well as decrypt.

Hope this helps you.

Thanks Parth Shah

0
source

More articles:


All Articles