CLI Analyzer does not use the configured proxy

[herbert-b]

Hi,

I installed CLI Analyzer 3.7.2 on a Windows host. On first run, it popped up an error "Internet can't be reached" so I went to the Advanced settings and configured my proxy (HTTP, URL and port).

After restarting the application, the error is still the same.
When I try "CCO Login" it opens my browser (which uses the same proxy) and I can authenticate to id.cisco.com just fine, it then opens CLI Analyzer again where I get an error "Unable to access Cisco cloud based services. Login Failed. Error code ECONNREFUSED"

When I run a packet capture on this host, I see that it's still trying to connect to a Cloudfront host directly on port 443 (which results in a RST from our firewall, which explains the ECONNREFUSED error).

Any idea how to fix this?

[balaji.bandi]

check this post :

https://community.cisco.com/t5/cisco-cli-analyzer/does-cli-analyzer-proxy-settings-support-automatic-configuration/td-p/4260828

[herbert-b]

Thanks but I don't see anything helpful (for my issue) in that thread. I'm not trying to get PAC or WPAD working or anything like that. I just configured a static proxy http://proxy.mydomain.com:3128 in the CLI Analyzer's advanced settings, but it's not using it ?

[Scott Hardin]

Hi,

Thanks for using Cisco CLI Analyzer!

There is a known issue with the current release of CLI Analyzer (3.7.2) where a configured proxy won't be utilized properly for the new CCO Login flow. I think this is the same issue you're having here. This will be fixed in the next CLI Analyzer release, which is currently being worked on.

Thank you for your patience,
Scott