No connection could be made because the target machine actively refused it - KB

News Knowledge Base
1

How to resolve the error 'Unable to connect to the remote server' while connecting UiPath Assistant to the Orchestrator?

Steps to investigate

  1. At the time of the error, analyze the application event log, if the error "No connection could be made because the target machine actively refused it (Orchestrator IP/Hostname:443)" is noticed.
  2. Make sure that the Orchestrator site is accessible on the Robot machine.
  3. Ensure all the services the Robot connects to have been added to allow list network configuration in the firewall, see outbound connections in the document Services The Robots Connects To.
  4. Check the 'Services' in the Robot machine to determine whether the Robot is installed in User Mode or Service Mode.

When in Service Mode, a Local System service named "UiPath Robot" can be located, which will not be present if installed in User Mode.

Resolution

If it is installed in Service Mode and the connection fails, then follow the below steps:

  1. Most likely, the Robot machine is behind a proxy. It can be checked from Proxy Settings (System).

  2. If proxy details are configured, then provide those details in the uipath.config file as per the Redirecting Robots Through A Proxy Server documentation.
    • Make sure the documentation page matches the version of the Robot that is installed.
  3. If the above configurations were already done but the issue persists, try removing the bypass-related key-value pairs from the config file, restart the Robot service and try connecting again.
    • It happens because Orchestrator might be configured as a local address and will not be routed through the proxy server if "bypass=true" for local addresses is enabled.

If the problem persists following the steps described, generate a Diagnostic Tool export and send it to support for review.

1 Like
2

The best guide , tysm