---
title: "Can't Connect to Target Machine - Actively Refused"
slug: "cannot-connect-to-target-machine-actively-refused"
updated: 2025-09-02T07:58:01Z
published: 2025-09-02T07:58:01Z
canonical: "support.controlup.com/cannot-connect-to-target-machine-actively-refused"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.controlup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Can't Connect to Target Machine - Actively Refused

## Issue

You try to connect to a ControlUp Agent, but it fails with the following error message:

          
          

Could not connect to xxxxx cuAgent. The connection attempt lasted for a time span of xx:xx:xx. TCP error code 10061: No connection could be made because the target machine actively refused it.

## Cause

The Real-Time Console tries to connect to an agent, but can't because the agent service is down. In **Agent Deployment Settings**, the **Deploy agents automatically** checkbox is deselected.

From the machine's action menu, if you click **Connect**, the console tries to connect. But if the agent service is down, it fails. ![machine action menu showing Connect](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/360011519078mceclip5.png)

## Solution

In order to fix the issue, the console needs to start the agent service when trying to connect. To automatically restart the agent's service when you connect, try the following solutions:

- From the machine's action menu, click **Agent Control** > **Upgrade/Install Remote Agent**:

![Agent Control Upgrade/Install Remote Agent](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/UpgradeAgent.png)

- Select the **Deploy agents automatically (from console only)**  option.