I have been having this error message for a while ...
# citrix-cloud
a
I have been having this error message for a while now, intermittent. Its a full clone VDI env, persistent single session. VDIs in vmware onprem and rest of the CTX infra in Citrix Cloud. Two cloud connectors.. Citrix support can't figure it out and I can't find any logs on this either. The only thing that Citrix support has told me so far that this is happening because the Cloud Connector is closing the connection for some reason.
b
Same here seeing this message for a while now on multisession VDA's. But i can not reproduce it.
j
Do you have rendezvous enabled? Could be one of the cloud connectors is dropping the session. This message is on the gateway side, not the endpoint from what I have seen.
a
Hey Jeff, not sure what you mean with rendezvous exactly, could you please tell me more? Yeah Citrix support is also saying that this shouldn't be on the endpoint side.
Rendezvous allows your connections from your cloud.com location to connect directly to the VDAs from the gateway service instead of being proxied through your cloud connectors. If users are on private networks connecting to cloud.com and have direct line of site to the VDAs, then you can enable Network Locations with your public NAT ip(s) to tell cloud.com to direct route to the resources.
a
I see that the STAs (cloud connectors) are using http:// on the netscaler gateway config ( wasnt me who configured the gateway). Shouldn't this be https?
j
Only if you went through the process to enable https for the STAs.
a
I would prefer not to enter the world of Rendezvous.. it seems to complicate things by quite a lot. I want to figure out where this is breaking..
j
Rendezvous is a game changer, you just need to enable it in Citrix Policies. Makes sessions run a lot smoother, and removes the proxy from the cloud connectors, which if they reboot can drop sessions proxying through them.
o
This was a bug with newer CWA combined with LTSR 2402 VDA where we were seeing it. Confirmed on Citrix side and they had private fix but don't think it made it into latest CWA. My fix was new VDA 2503 (as next ltsr is right around the corner anyway) and that fixes it. That's my two cents
a
Hey Oz Zy, I am already running 2503 VDAs though 😕
o
No idea. We had that on 3 different environments that were tied to CWA 2501.x with 2402 VDA (not sure exactly if certain CU as we couldn't recreate it with working it with the back end team) In our situation a new install (not upgrade) of VDA 2503 was workaround to get it fixed right away so we were only then troubleshooting still with the older 2402 VDA to help TRY and recreate it for escalation support.