New issue
Advanced search Search tips

Issue 868430 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 31
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

ERR_PROXY_CONNECTION_FAILED

Reported by will.mcd...@googlemail.com, Jul 27

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Unable to reproduce error; it happens randomly
2. 
3. 

What is the expected behavior?
Users to be able to access internet without 'ERR_PROXY_CONNECTION_FAILED' error.

What went wrong?
We use a proxy server (Smoothwall) to route our users internet access.
We've deployed Chrome GPO templates to set Chrome to look at system setting for proxy details - the system is set to 'automatically detect'.

Since Chrome 66 we've had a problem where Chrome will show 'ERR_PROXY_CONNECTION_FAILED' message.
Other browsers like Edge, Internet Explorer and Firefox work without issue.
Oddly, if a new tab is opened within Chrome that will work, but the tab with 'ERR_PROXY_CONNECTION_FAILED' message will not load no matter how often you try to refresh it.
You can actually copy and paste the URL into a new tab and it works.

I've since changed the Chrome GPO to declare the location of the .pac file - we still see this error.

Did this work before? Yes 64 / 65

Chrome version: 67.0.3396.99  Channel: stable
OS Version: 10.0
Flash Version: 

We're currently starting our Windows 10 project around 2400 users.
We intend to set Chrome as the default browser but this error is making us worry!
 
Components: Internals>Network>Proxy
Next time you observe the issue please navigate in a separate tab to chrome://net-export/ and start capturing events there. While this is on do a few attempts at loading stuff in the broken tab. Then upload the log here (or if you decided to include personal information you can share it directly with some of the engineers through drive, dropbox or your preferred mean.
To add to comment #1's instructions:

While a capture is in progress, please also click the "Re-apply Settings" button on chrome://net-internals/#proxy and then try to reproduce the issue again to see if things change.
I reviewed the Chrome network log after the issue occurred.

I noticed it was failing to resolve WPAD in DNS:

t=   2 [st=   0] +HOST_RESOLVER_IMPL_JOB  [dt=2256]
                  --> host = "wpad"
                  --> source_dependency = 7678 (TRANSPORT_CONNECT_JOB)
t=   2 [st=   0]    HOST_RESOLVER_IMPL_JOB_STARTED
t=   2 [st=   0]   +HOST_RESOLVER_IMPL_PROC_TASK  [dt=2256]
t=   2 [st=   0]      HOST_RESOLVER_IMPL_ATTEMPT_STARTED
                      --> attempt_number = 1
t=   2 [st=   0]      HOST_RESOLVER_IMPL_JOB_REQUEST_ATTACH
                      --> priority = "IDLE"
                      --> source_dependency = 7678 (TRANSPORT_CONNECT_JOB)
t=   2 [st=   0]      HOST_RESOLVER_IMPL_JOB_REQUEST_ATTACH
                      --> priority = "IDLE"
                      --> source_dependency = 7683 (TRANSPORT_CONNECT_JOB)
t=2258 [st=2256]      HOST_RESOLVER_IMPL_ATTEMPT_FINISHED
                      --> attempt_number = 1
                      --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
                      --> os_error = 11001
                      --> os_error_string = "No such host is known.\r\n"
t=2258 [st=2256]   -HOST_RESOLVER_IMPL_PROC_TASK
                    --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
                    --> os_error = 11001
                    --> os_error_string = "No such host is known.\r\n"
t=2258 [st=2256] -HOST_RESOLVER_IMPL_JOB
                  --> net_error = -105 (ERR_NAME_NOT_RESOLVED)
-------------------

About a month ago we started to load balance our DNS queries via NetScaler to our Active Directory DNS servers.
WPAD was on 'DNS block list' on all but 1 server (out of 4).
We've removed this record from the block list and so far no complaints... I'm waiting for 7 days before I confirm it's working.

I wasn't aware of net-export, this has helped identify a cause - thanks for that.

I'll post back this time next week to confirm it's resolved.

Thanks
Status: WontFix (was: Unconfirmed)
Thanks for the update!
I will tentatively mark this as closed.

To be getting ERR_PROXY_CONNECTION_FAILED implies that the (system) proxy setting you are using specifies both auto-detect AND an explicit proxy server. Since auto-detect is best effort (except when configured as mandatory in Chrome).

Sign in to add a comment