In some environments, users may encounter connection failures to a Virtual Delivery Agent (VDA) in Citrix Cloud DaaS.
VDA and Cloud Connectors are in the same zone.
One common cause is port 443 already being used by another service on the VDA, which prevents the required Citrix components from binding to the port.
This article explains how to identify the process using port 443 and release the port if the service is not required
Step 1: Verify which process is using port 443
Step 2: Identify the service/application using the PID
Step 3: Check if IIS is Running on the VDA
Option 1: Using Command Prompt
Option 2: Using Services Console
Step 4: Stop the Service Occupying Port 443
If IIS is not required on the VDA and is occupying port 443, stop the service.
Option 1: Using Command Prompt
Note: Before stopping the service, confirm that IIS or the service using port 443 is not required by any business-critical application running on the server
Step 5: Re-validate port 443 availability
Once port 443 is released, the VDA can successfully listen for connections from the Cloud Connectors, allowing the published desktop launch to proceed normally.
Unable to launch the published desktop in Citrix DaaS and encountered a “Connection Refused to VDA” error during the launch attempt.
Event logs on the Virtual Delivery Agent (VDA) showed “VDA connection refused” messages.
This occurred even though the VDA and the Cloud Connectors were configured within the same zone, indicating that the issue was not related to zone placement but likely due to connectivity or service configuration between the components.