The Orchestrator URL opens successfully in the browser, but when connecting through UiPath Assistant, I receive the following error:
“A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”
Troubleshooting Done:
- URL opens in browser
- Network connectivity verified
- Restarted UiPath Robot Service
- Checked firewall
Request:
Could someone help identify whether this is related to proxy, SSL certificate, or Robot configuration?
Hi @Pavan123 ,
Since Orchestrator works in the browser but UiPath Assistant times out, first check the Robot/Assistant proxy configuration. Browser access alone does not confirm that the Robot service is using the same proxy. For a Service Mode Robot, UiPath requires the proxy to be configured for the Robot as well as the relevant Windows user settings.
Also verify that the SSL certificate used by the on-prem Orchestrator is trusted by the Robot machine, especially if a self-signed/internal certificate is being used. UiPath recommends a CA-issued SAN certificate for HTTPS communication between Orchestrator and Robots.
After correcting the proxy/certificate configuration, restart the Robot service and reconnect Assistant.
From the screenshot, I noticed that the Assistant is configured with UiPath Platform URL → https://cloud.uipath.com, while the post mentions an on-prem Orchestrator. Could you confirm whether you are actually trying to connect to your on-prem Orchestrator or to UiPath Automation Cloud?
If it is the on-prem Orchestrator, please verify that the correct Orchestrator URL is configured in Assistant. If the URL is correct, I would then check the Robot Service proxy configuration and SSL certificate trust, since browser connectivity does not necessarily mean the Robot Service has the same network/proxy access.
Also, checking the Robot/Assistant logs at the time of the timeout may help identify whether the failure is occurring at the proxy, SSL, or connection level.
This is better because you’re pointing out something specific visible in their screenshot, rather than giving only generic troubleshooting steps.
Hi @Pavan123, like @MayureshOfficial_45 mentioned, your Platform URL still points to https://cloud.uipath.com, so Assistant is trying Automation Cloud instead of your on-prem server. In Preferences > Orchestrator Connection, put in the exact on-prem URL that works in your browser and sign in. For an unattended robot in Service Mode, use Machine Key with that URL instead. Assistant - Preferences
Hi @Pavan123, This is a timeout error, so Assistant is not getting any reply from the server. Browser working does not mean the Robot can also reach it.
Please check these two things:
URL: In your screenshot, the Platform URL is https://cloud.uipath.com (as Mayuresh and Pravinraj also said). That is Automation Cloud, not your on-prem server. Go to Preferences > Orchestrator Connection and enter the same Orchestrator URL that you open in the browser. If your Robot is in Service Mode, connect using Machine Key.
Proxy: If your company uses a proxy, the Robot also needs it. In Service Mode (Robot 2025.10), set it in proxy.json at %ProgramData%\UiPath\Shared, then restart the Robot service.
