The number of certificates can become quite large after using Fiddler for a while, depending on how many different websites you visit. This is effectively a legitimate use of the Man-in-the-middle attack technique. The short explanation is that allowing Fiddler to capture HTTPS traffic results in creating a fake Certificate for each website that it intercepts. Several more attempts yielded the same result.Ī quick search turned up a fantastic explanation of the problem by Matt LaPaglia. Eventually, it timed out and the VPN connection failed. This message stayed around without changing and without any other sign of activity. Rather than connecting and prompting me for my credentials, the An圜onnect client showed me this message: Several days after starting work for this client, I experienced a problem when I attempted to connect to the VPN one morning. This is a pretty common scenario for many remote workers. I also use Cisco An圜onnect VPN to connect to the network of my client. There are plenty of postings about this technique, but here’s short one that gets right to the point. This is a big deal when writing custom code inside the Microsoft Dynamics CRM ecosystem. This saves a huge amount of time by allowing me to simply build (transpile) locally without having to upload the changed files after every edit. I use Fiddler on a daily basis to redirect requests for external web resources back to my local machine. Jump to The Solution or read on for details… The Scenario

Clearing these certificates will resolve this error. Fiddler creates a LOT of certificates when you allow it to intercept HTTPS traffic.

Cisco An圜onnect VPN software fails to connect with the error “Hostscan is waiting for the next scan” when there are too many certificates in your Personal Certificates folder.

Cisco anyconnect vpn login failed