Hi UiPath Community,
I wanted to share a simple infrastructure-level explanation of how UiPath Robot connects to Orchestrator. This may help beginners and infrastructure engineers troubleshooting connectivity issues.
Core Components Involved:
-
UiPath Robot Service (Windows Service)
Installed on the robot machine. It runs in the background and manages communication. -
Machine Key / Machine Template
Used for authenticating the robot machine with Orchestrator. -
UiPath Assistant
User interface that interacts with the Robot Service. -
Orchestrator (Hosted on IIS / Automation Cloud)
Central server managing robots, processes, queues, and assets.
Connection Flow:
Robot Service → HTTPS (Port 443) → Orchestrator URL → Identity Server → Authentication → Robot Connected
Common Infrastructure Issues:
• Incorrect Machine Key
• Firewall blocking outbound HTTPS (443)
• SSL certificate issues
• Incorrect Orchestrator URL
• Robot service not running
• Identity Server misconfiguration
Infrastructure Troubleshooting Steps:
- Verify Robot Service is running (services.msc)
- Verify Orchestrator URL is accessible in browser
- Check firewall allows outbound HTTPS
- Restart UiPath Robot Service
- Verify machine template assignment in Orchestrator
Infrastructure engineers should also monitor:
• IIS Application Pool status
• SQL Server connectivity
• SSL certificate validity
I hope this helps anyone troubleshooting robot connectivity.
Happy automating!