Communication times out while forwarding to RemoteHcl WCF server

Specify the cloud connector FQDN in the WinHTTP proxy bypass list. The following example shows the addition of the cloud connector with an FQDN of `bvcchard2.hardening.local` to the WinHTTP proxy bypass list:


After setting the bypass list, restart the cloud connector to apply the new WinHTTP settings.

Important

When specifying the bypass list, use semicolons, not commas, to separate the items in the list. The netsh winhttp set proxy command accepts the comma syntax, but the resulting bypass list is ignored. Do not use “*” wildcards when performing this operation.

For example:

netsh winhttp set proxy proxy-server=”http=10.10.10.50:8080;https=10.10.10.50:8080″ bypass-list=”<-loopback>;bvcchard2.hardening.local”

In the example above, the IP addresses are the proxy server and port.

Related:

Communication times out while forwarding to RemoteHcl WCF server (HclOverWebsockets feature toggle enabled)

Specify the cloud connector FQDN in the WinHTTP proxy bypass list. The following example shows the addition of the cloud connector with an FQDN of `bvcchard2.hardening.local` to the WinHTTP proxy bypass list:


After setting the bypass list, restart the cloud connector to apply the new WinHTTP settings.

Important

When specifying the bypass list, use semicolons, not commas, to separate the items in the list. The netsh winhttp set proxy command accepts the comma syntax, but the resulting bypass list is ignored. Do not use “*” wildcards when performing this operation.

For example:

netsh winhttp set proxy proxy-server=”http=10.10.10.50:8080;https=10.10.10.50:8080″ bypass-list=”<-loopback>;bvcchard2.hardening.local”

In the example above, the IP addresses are the proxy server and port.

Related:

Site aggregation fails with error “We couldn't find your site”

This issue is seen because the Proxy logic in the Citrix Cloud Connector expects all the entries in Proxy By-Pass list in all lower case and hence fails to process the entire Proxy By-Pass list, if even one entry is in All Capital or Mixed case.

Due to this, the Web Relay agent services reach out to the Proxy Server to contact the XML Service running on the On-Prem delivery controller.

Since the Proxy servers are not configured to resolve the internal FQDNs, the above service is unable to resolve the Delivery controller addresses and hence the site aggregation fails.

Related:

  • No Related Posts

Proxy Gateway potentially causing website performance issues

I need a solution

Hi everyone

I hope someone can help me with a rather puzzling issue.

We have a website, collaborative.eversheds-sutherland.com 213.212.88.203 which users can connect but experience very slow performance when navigating around the site. This only occurs when they are on the network. Performance when accessed from home or another non-network source is absolutely fine.

From what I can tell, traffic leaves our network via the firewall (bypassing the proxy). This proxy override has also been enabled on Group Policy for this website. However, the puzzling thing is that I’m still seeing active sessions for this website on the Bluecoat Proxy Gateway. I believe the traffic is coming back through the Proxy but I can’t see why.

Gateway details: 

ProxySG 810-10 SGOS 6.5.3.6 Proxy Edition

Is there anything I can check on the Bluecoat? Like I say connectivity is there but the website performance is very slow. When users use the developer tools in the browser to inspect the site, they commonly see the following errors:

ERR_TUNNEL_CONNECTION_FAILED

CORS Policy Error

I’ve looked up both of these errors and they both point to a proxy issue but I cannot work out what it could be. I’ve attached a screenshot which shows the active sessions currently on the BC Gateway. The Gateway IP is 10.20.48.100 but each different office has it’s own BC Proxy server that does it’s own web filtering. The one on screenshot is from the London office.

 I’d appreciate any assistance as this is proving to be a huge issue for me.

Many thanks

B

0

Related:

How can I force “client.wns.windows.com” through my proxy. It does not seem to be proxy aware.

I need a solution

Hi;

A connection to “client.wns.windows.com” is bypassing the Proxy SG, going straight to the internet as the Proxy SG is setup to receive explicit connections from browsers.

I am not sure what application is sending this connection, but it does not seem to be “Proxy Aware”. 

Kindly

Wasfi

0

Related: