Troubleshooting Error PHOENIX 187: Phoenix Agent Unable to Connect to Druva Cloud

Problem Description

The Phoenix Agent fails to communicate with the Druva Cloud, resulting in a PHOENIX 187 error. This is a general communication failure typically triggered when the agent cannot synchronize status or backup data.

Symptoms

The workload status in the Druva Management Console shows as Disconnected.
Backup jobs fail immediately with Error Code: PHOENIX 187.
The error description often reads: "The Druva Phoenix agent is unable to connect to the Druva Cloud."

Root Cause

This error is usually caused by one of the following:

Service Disruption: The Druva service is stopped on the local workload.
Network Restrictions: Firewall or proxy settings are blocking communication over Port 443.
Security Software: Antivirus or EDR solutions are killing or blocking Druva processes.

Resolution Steps

Step 1: Verify Agent and Service Status

Ensure the Druva service is active on the source machine.

Windows:
1. Open services.msc.
2. Locate Druva Enterprise Workloads.
3. Ensure the status is Running. If not, right-click and select Start or Restart.
Linux:
1. Open a terminal.
2. Check status: sudo /etc/init.d/DruvaEnterprise Workloads status
3. If inactive, restart: sudo /etc/init.d/DruvaEnterprise Workloads restart

Step 2: Check Network Connectivity

The agent requires a persistent outbound connection to the Druva Cloud via Port 443.

Connectivity Test (Windows PowerShell):
Test-NetConnection phoenix.druva.com -Port 443
Verify that TcpTestSucceeded is True.
Connectivity Test (Linux):
nc -v phoenix.druva.com 443 or telnet phoenix.druva.com 443
Whitelisting: Ensure *.druva.com is whitelisted in your firewall/proxy.

Step 3: Investigate Third-Party Interference

Security software may flag Druva as a false positive.

Review Logs: Check Antivirus/EDR logs for blocked processes, specifically PhoenixFSBackupAgent.exe.
Exclusions: Add exclusions for the following paths:
- Windows: C:\Program Files\Druva
- Linux: /opt/Druva

Step 4: Manual Trigger and Log Collection

Navigate to the Druva Management Console.
Go to File Servers and attempt a Manual Backup.
If the error persists, select the server and click Upload Logs to send diagnostic data to Druva Support.

Verification

Once resolved:

The server status in the Console should change to Connected.
Manual backup jobs should complete with a Successful status.