Overview

Server-workload connectivity has been interrupted preventing the completion of workload activity. Agent Proxy logs surface the following error message, "ERROR aembit_proxy::protocols::tcp_passthrough - Could not connect to the server workload: Connection refused (os error 111)"

Relates To

• Server Workload
• Workload Events
• Access Policy

Causes

The error signature reflects a range of entry points for remediation. We recommend reviewing these areas of interest to validate your configuration, ingress/egress setup, and environmental network activity.

• Access Policy
  • Policy configuration - Client Workload, Trust Provider (optional), Credential Provider, Server Workload
• Server Workload
  • Target Destination
  • IP, Port
  • Hostname
• Agent Proxy
  • Variables - Review values
• Environment
  • Network - Activity spikes, updates or maintenance

Solution

1. To investigate, we should start by enabling 'debug' log level. See details below in the related Knowledge base article, here.
   1. Debug level tracing provides granular details at various phases of Agent Proxy or Agent Controller activity.
2. We recommend reviewing communication between Agent Proxy and Agent Controller to ensure Edge Components are operating as expected.
   1. If Agent Proxy registration is failing, review the technical information found Troubleshooting Agent Proxy Registration
3. To analyze the behavior between your Client Workload and Server Workload, we detailed steps on troubleshooting an Access Policy outlined in the following article, Troubleshooting an Access Policy.
   1. 1. We recommend reviewing
         1. The checks performed by our Troubleshooter tool
         2. Reviewing the accuracy of data fields populated for each component in your access policy
         3. Confirming Network activity to target Server Workload for any erroneous activity