Hi @kauveryrpabot ,
The error “No connection could be made because the target machine actively refused it” usually means UiPath Assistant cannot reach the Orchestrator/Automation Cloud URL.
Things to check:
Verify the Orchestrator URL is correct. It looks like a Monitoring page URL was pasted instead of the base Orchestrator URL.
Open the URL in a browser and confirm it is accessible from your machine.
Check if a Firewall, Proxy, VPN, or Corporate Network policy is blocking the connection.
Ensure UiPath Assistant and Robot services are running. Restart the UiPath Robot Service and try again.
Sign out from UiPath Assistant and sign in again.
Clear Assistant cache (%AppData%\UiPath) and reconnect if the issue persists.
If using a self-hosted Orchestrator, verify the server is online and the required ports (HTTPS 443) are reachable.
From what I see in your screenshot, you are using a UiPath Automation Cloud URL, so there are the following configuration possibilities depending on the license you use:
Once this is clarified, if you are still having issues with logging in, I recommend performing the following connectivity tests with the platform. To do this, run the following PowerShell commands from your computer (to open a PowerShell window, press the key combination WINDOWS + R and run the command powershell):
Check HTTPS connectivity to the UiPath Automation Cloud platform: Test-NetConnection -ComputerName cloud.uipath.com -Port 443
Check the status of the identity server of the UiPath Automation Cloud platform: Invoke-WebRequest https://cloud.uipath.com/identity_/.well-known/openid-configuration -DisableKeepAlive -UseBasicParsing -Method Get
The issue is the URL you’ve pasted into the “UiPath Platform URL” field. Replace it with just the base cloud URL and organization (tenant logical name), e.g.: https://cloud.uipath.com/kauvevawzykk
Here are the steps for you to perform:
Clear the current URL in that field.
Enter https://cloud.uipath.com/<your-organization-logical-name>.
Click Sign in again and complete the browser-based login.
If the above steps don’t fix your issue, then check these out as well.
Make sure you have internet connectivity and no corporate proxy/firewall is blocking cloud.uipath.com.
If your org uses a specific tenant, you don’t put the tenant in this field at all, tenant selection happens after sign-in, inside the Assistant.