Chrome is not working through WSA 170

[tarun.singh7]

Chrome is not working through WSA 170 but it work through other proxy.

[Tao Yang]

Chrome is just a browser. Please provide more details of your issue.  

[pikovic41]

Hello,

I have same issue, in brief the access policy on WSA working fine with IE for block sites and show wsa page for blocking , while the Chrome and Firefox give me error only and not show wsa block page 

the cerificate is okay on machine , wsa version is the latest 10.1.1

please advice 

thanks 

[Robert Sherwin]

This is a known issue w/ Chrome.  We do have a workaround, if you can open a support request and provide remote access to the appliance - Cisco TAC does have a script that can be implemented in order to temporarily correct this on the WSA.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf51310/?referring_site=bugquickviewredir

[keithsauer507]

Even with the tampermonkey script, Chrome will log in but then load some script HelpBarYUI_js.

[billlippai]

Ran into this same issue in Internet Explorer after upgrade where upon logging in to the WSA, received a message Do you want to save HelpBarYUI_js.js from xxx. Clicking save and open resulted in a missing YAHOO popup message. Once into the page, the menu tab bars worked but the top menu options for help/logout did not work.

Had some other devices that were upgraded that were working without this error. Difference was that working devices on that version were referenced by https://<IP address>:8443/ worked and those referenced by http://<device name>:443/ did not. Found using the IP address in the link worked so that the prompt was no longer there and the menus worked properly.