Problem Description
When attempting to configure a network web proxy or activate the EnterpriseWorkloadsAgent, the operation fails. You may notice one of the following indications:
Desktop Graphical Application: The EnterpriseWorkloadsAgent desktop shortcut layout opens to a completely blank window, rendering no parameters to configure the web proxy or complete registration.
Command Line (Proxy Config): Executing the configuration parameters through an elevated command prompt falls back onto the following error payload:
Failed to set proxy configuration: Put "https://localhost:8082/falcon/v1/webProxy": http: server gave HTTP response to HTTPS client
Command Line (Activation): Standard manual activation runs via the command prompt (even following an offline alteration of the configuration template) return:
Plaintext
"https://localhost:8082/falcon/v1/webProxy": http: server gave HTTP response to HTTPS client
Cause
This condition is triggered because the default port reserved for local microservice hooks within the EnterpriseWorkloadsAgent daemon (Port 8082) is already actively bound to a separate, non-Druva process on the target server environment.
Resolution
To remediate this conflict, you must pinpoint a free local TCP port on the host operating system and redirect the agent service configuration tracker to utilize that path.
Step 1: Confirm the Port Block
Open an elevated Command Prompt (Run as Administrator).
Execute the following sequence to isolate active processes binding port 8082:
netstat -ano | findstr 8082
If this strings back alphanumeric rows showing listening PIDs, the default port is contested.
Step 2: Identify an Alternate Open Port
Scan an alternative unassigned port target (for example, 8083) to ensure it is completely free:
netstat -ano | findstr 8083
(If no output or rows return, this port is open and safe to adapt.)
Step 3: Update the Agent Configuration Mapping
Open the Windows Services Management Console (
services.msc).Locate and Stop the
Druva-EnterpriseWorkloadsservice wrapper.Access the file system tracking paths using File Explorer or a terminal interface:
C:\ProgramData\Druva\EnterpriseWorkloads\
Open the
Config.yamlcore definition manifest in an text editor (e.g., Notepad) leveraging elevated Administrator permissions.Locate the variable string attribute labeled
service_portand modify its value to match the open port determined during Step 2.service_port: 8083
Save your edits and close out of the text editor workspace.
Return back to the Windows Services applet (
services.msc) and Start theDruva-EnterpriseWorkloadsservice.
Step 4: Re-Run Agent Activation
Relaunch the registration process through the administrator shell framework using your designated organizational token string:
EnterpriseWorkloadsAgent.exe fs activate --token <your_activation_token>
The activation wrapper will successfully initialize, bind correctly to the altered local port endpoint, and the server instance will cleanly surface within your Druva Management Console interface.