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:

Error: “Previous Upload to cis.citrix.com failed. Network Error While Connecting cis.citrix.com” with Code 10


The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: Previous Upload to cis.citrix.com failed. Uploader failed for reason “Network Error while connecting cis.citrix.com” with code 10


The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: “Previous Upload to cis.citrix.com Failed. Network Error While Connecting cis.citrix.com” with Code 6

The error message indicates that the Call Home upload toCitrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server toCitrix.com, or the presence of a Firewall or Network Proxy in the environment.


To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

License Server – Call Home Failing and Logging an Error in Director – Uploader Failed “Network SSL Error When Connecting to citrix.com” Code 7

The error message indicates that the Call Home upload tocis.citrix.comfailed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server tocis.citrix.com, or the presence of a Firewall or Network Proxy in the environment.

To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect tocis.citrix.comover port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps:Configure a Proxy server.Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reachcis.citrix.comfrom the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse toC:Program Files (x86)CitrixLicensingLSresourceusagefolder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart theCitrix Webservice for Licensing servicefrom the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined inCTX220679

Related:

Error: “Previous Upload to cis.citrix.com Failed. Network Error While Connecting cis.citrix.com” with Code 5

The error message indicates that the Call Home upload to Citrix.com failed. This can happen due to multiple reasons, including there was simply no connectivity from the License Server to Citrix.com, or the presence of a Firewall or Network Proxy in the environment.

To troubleshoot the underlying cause of the failure, please follow the steps below:

  1. Make sure the License Server has network connectivity and can connect to cis.citrix.com over port 443
  2. If you will have to configure a proxy, please refer to the following documentation for the steps: Configure a Proxy server. Please note that Licensing service needs to be restarted for the changes to take effect.
  3. If there are no proxies required to reach cis.citrix.com from the server, it is possible that there was a network error at the time of upload attempt and that has been resolved since then. Once an upload fails, the Upload failure status is tracked through an XML file (Upload_result.xml). So even when the network issue is resolved or when Call Home is subsequently disabled after an upload failure, unless the XML file is manually deleted, you will continue to see the error. The following steps will get rid of the error message:
    1. Browse to C:Program Files (x86)CitrixLicensingLSresourceusage folder.
    2. Take a copy of the contents of this folder for backup purposes and empty this folder.
    3. Restart the Citrix Webservice for Licensing service from the Services console.
  4. If none of the steps above resolved the issue, you can disable Call Home following the steps outlined in CTX220679

Related:

Longer than usual launch duration of Virtual App and Desktop while using Citrix Gateway Service

After 18th May, 2020 users with the following registry key set to “Preferred” can attempt to initiate an EDT connection. As EDT is not yet provisioned by admin, it will take few seconds for the connection to fallback to TCP, causing the delay.

HKEY_CURRENT_USERSoftwareCitrixIca ClientEngineLockdown ProfilesAll RegionsLockdownNetworkEDT

HKEY_CURRENT_USERSoftwarePoliciesCitrixIca ClientEngineLockdown ProfilesAll RegionsLockdownNetworkEDT

HKEY_LOCAL_MACHINESoftwareCitrixIca ClientEngineLockdown ProfilesAll RegionsLockdownNetworkEDT

HKEY_LOCAL_MACHINESoftwarePoliciesCitrixIca ClientEngineLockdown ProfilesAll RegionsLockdownNetworkEDT

On 64 bit machine

HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientEngineLockdown ProfilesAll RegionsLockdownNetworkEDT

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: