Problem description
Druva and SQL Server Reporting Services (SSRS) are both configured to use port 8082, resulting in a port conflict. This may lead to Druva backup failures, agent startup issues, or service unavailability.
Cause
A port conflict occurs when multiple services attempt to use the same network port (in this case, 8082). Since both Druva and SSRS are using port 8082, only one service can bind successfully, causing the other to fail.
Traceback
Druva service may fail to start or show errors similar to:
Failed to bind to port 8082
OR
Port already in use
Solution
To resolve the port conflict, change the port number Druva uses by following the steps below:
Stop Druva Services
Open Services and stop all Druva-related services.Navigate to the Configuration Directory
Path:
C:\ProgramData\Druva\EnterpriseWorkloads\Edit the Configuration File
Open the file Config.yaml in a text editor (e.g., Notepad).
Locate the following line:
service_port: 8082Change 8082 to another available and unused port, e.g., 8083.
Save the File
Restart Druva Services
Start all previously stopped Druva services.
Note:
Ensure the new port:
Is not in use by another application.
Is allowed through the system firewall and any network security tools.