forgot to mention - we are using symantec web filtering which uses an on site squid proxy

remove enterprise component.

I'm having a similar issue, it may be the same one, and so far my solution has been to downgrade to chrome 67.

For Chrome 69:

1. Put in a proxy that requires authentication via chrome extension (even system proxy causes this). You will get prompted for the username and password on the first request.
2. Hit cancel and close the browser.
3. Open the browser again, and you are never asked for credentials. Instead, you just get err_tunnel_connection_failed (I believe was the error) forever.

Could you get us a net-internals log as described here? https://dev.chromium.org/for-testers/providing-network-details

Please find logs attached.

Deleted: proxy-blocked.json 627 KB

proxy-blocked.json 627 KB View Download

Deleted: proxy-works.json 892 KB

proxy-works.json 892 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on reported chrome version 69.0.3497.81  also on latest chrome 71.0.3548.0 using Mac 10.13.5, Ubuntu 17.10 and Windows 10 & 7.  

Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Removing Needs-Bisect label to it.

Thanks! 

It seems like this issue is present with IWA-based authentication.  Chrome is not responding to authentication requests from on-prem proxies.

Just to add we are experiencing this as well. Receiving err_tunnel_connection_failed as the proxy authentication prompt never appears. We have an on premise squid based proxy using basic authentication.

We have reverted back to 68.0.3440.106 as authentication prompts appear correctly for this version.

We find the trigger is visiting a site on white list that goes through proxy without needing authentication and then visiting a site that requires proxy login. The login prompt does not appear when required.

In attached test case http://www.airserver.com/ is on white list and https://www.originenergy.com.au/ requires authentication through proxy.

(Replacing file that seemed to be missing lines)

Deleted: chrome-net-export-log2.json 4.2 MB

chrome-net-export-log2.json 4.2 MB View Download

I've been having this issue to. Is there any way to stop Chrome from updating every 15 minutes? I prefer using an older version of Chrome that works.

Just to confirm we are still experiencing issue on 70.0.3538.67.
As this affects all users we are unable to roll out anything later than 68 until resolved.

Regarding comment 15 about not updating, you can download deployment bundles from https://www.google.com/intl/en/chrome/business/browser/admin/ that include group policies that can be used to block updates.