[Infrastructure Troubleshooting] UiPath Robot Showing Disconnected / Unavailable in Orchestrator – Complete Resolution Guide

Help Orchestrator
, , , , ,
1

Hi UiPath Community,

One of the most common infrastructure issues is when UiPath Robot shows as “Disconnected” or “Unavailable” in Orchestrator.

This prevents automation execution and indicates a platform connectivity problem.

Based on infrastructure troubleshooting experience, here is a structured checklist to identify and resolve the issue.

Understanding the connection architecture:

UiPath Robot Service (Windows Service)
↓
Secure HTTPS Connection (Port 443)
↓
UiPath Orchestrator
↓
Identity Server Authentication
↓
Robot Connected State

If any component fails, robot shows as Disconnected.

Root Cause 1: UiPath Robot Service is stopped

Resolution:

Open Services on robot machine:

services.msc

Find:
UiPath Robot

Ensure Status = Running

If stopped, start the service.

Recommended: Restart the service to refresh connection.

Root Cause 2: Incorrect Orchestrator URL configuration

Resolution:

Open UiPath Assistant

Check Orchestrator URL:

Example:

Ensure correct tenant and URL.

Test URL in browser to confirm accessibility.

Root Cause 3: Firewall blocking outbound HTTPS connection

Robot requires outbound HTTPS (Port 443).

Resolution:

Check firewall rules

Ensure outbound access to:

cloud.uipath.com

or your Orchestrator server URL

Blocked firewall prevents robot authentication.

Root Cause 4: Machine Template or Machine Key mismatch

Resolution:

Go to Orchestrator → Tenant → Machines

Verify:

Machine Template exists
Machine Key matches robot machine configuration

Incorrect machine key causes authentication failure.

Root Cause 5: Identity Server authentication failure

Identity Server handles robot authentication.

Resolution:

Verify Orchestrator is accessible

Re-login UiPath Assistant

Sign out and reconnect machine.

Root Cause 6: DNS resolution issue

Resolution:

From robot machine, test:

ping cloud.uipath.com

If DNS fails, check network and DNS configuration.

Recommended infrastructure troubleshooting steps:

  1. Restart UiPath Robot Service
  2. Verify Orchestrator URL access
  3. Verify firewall outbound HTTPS
  4. Verify Machine Template configuration
  5. Verify network connectivity

Conclusion:

Most Robot Disconnected issues are caused by:

• Robot Service stopped
• Firewall blocking HTTPS
• Machine Key mismatch
• Incorrect Orchestrator URL
• Network connectivity issues

Following this checklist helps quickly restore robot connectivity.

Hope this helps anyone troubleshooting UiPath Robot infrastructure connectivity.

Nandri,
Muthuraman G

1 Like
2

Hello @muthuraman.g!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff