I am attempting to set up UiPath Studio inside a Virtual Machine(VM) and connect it to Orchestrator, but i am encountering a connection timeout error during the sign-in prompt.
Error Details:
“A connection attempt failed because the connected party did not properly respond after a period of time, or establised connection failed because connected host has failed to respond.”
Troubleshooting done:
Browser Reachability :- I opened Microsoft edge inside the same VM and navigated to the Orchestrator URL- the Orchestrator page loads successfully in the browser.
Interactive Sign-in :- When attempting interactive sign-in via UiPath Studio using the service URL, it timeouts repeatedly after a delay.
Environment :- UiPath Studio installed inside a VM environment.
Any guidance on resolving this or best practices for connecting Studio inside a corporate VM would be greatly appreciated!
@Mohed_Rehan_Khan Since Orchestrator is opening in the browser but Studio sign-in is timing out. Please try the below steps:
Open PowerShell and run: Test-NetConnection -Port 443 Expected: TcpTestSucceeded should show True.
Check the proxy used by Windows/Studio: netsh winhttp show proxy If your organization uses a proxy but this shows Direct access, Studio/Robot may not be using the same proxy configuration as Edge.
Compare with the browser proxy
Go to: Windows Settings → Network & Internet → Proxy
Check whether a proxy or automatic configuration script is configured there. If this is a corporate VM, I would ask the network team before changing these settings.
Check UiPath logs
%LocalAppData%\UiPath\Logs
Reproduce the Studio login issue and then check the latest log file. Look for entries containing:timeout
connection
proxy
SSL
certificate
identity
Check how the Robot is installed. If it’s Service Mode, interactive sign-in may not work. In UiPath Studio/Assisstant use More Options > Connect to Orchestrator with Client ID/Secret or Machine Key instead. Also, check if “UiPath.Service.Host” process is running.
One more thing that may cause these issues is the Windows Firewall is blocking the localhost callback port on the VM.
@Mohed_Rehan_Khan
since Orchestrator opens correctly in the browser but Studio times out, I’d compare the proxy used by Windows/Studio with the one used by the browser.
Check netsh winhttp show proxy and test port 443 from the VM. If connectivity is OK, reproduce the login and check %LocalAppData%\UiPath\Logs for proxy, SSL, certificate or identity errors.
You can also try signing in from UiPath Assistant. If Assistant fails in the same way, that would point more toward the VM/proxy configuration than Studio itself.
Since the Orchestrator URL is accessible from the browser inside the VM, I would first check the VM-specific network/proxy configuration.
Please verify whether the VM is using a corporate proxy and whether UiPath Studio is configured to use the same proxy. Also check that outbound HTTPS (443) communication to the required UiPath services is allowed.
If possible, you can also try Connect to Orchestrator using the appropriate machine/client credentials instead of interactive sign-in, to isolate whether the issue is specifically with the interactive authentication flow.