- Release Notes
- Getting Started
- UiPath Assistant
- Installation and Upgrade
- Robot Types
- Robot Components
- Licensing
- Connecting Robots to Orchestrator
- Processes and Activities
- Logging
- Robot JavaScript SDK
- Specific Scenarios
- Troubleshooting
Services the Robot Connects to
During the workflow execution, the Robot connects to different services to download required automation packages, check licences, verify certificates, and more. Denying access to any of these services can result in operation discrepancies, or even failure. The connection is established in the following cases:
- The Robot validates license details on the machine it is installed on and shares only license-related information with the licensing server.
- The Robot downloads the required automation packages.
The UiPath Robots connect to different services, such as:
Hostname |
Protocol |
Port |
Application |
Comments |
---|---|---|---|---|
cloud.uipath.com
|
TCP |
443 |
https |
For Automation Cloud Orchestrator. |
myget.org
|
TCP |
443 |
https |
The Robot downloads the required activity packages. |
activate.uipath.com
|
TCP |
443 |
https |
Licensing Server. If we block this service then UiPath is not able to check the license status and verify the data in the license folder. |
jptk0*.proinity.net
|
TCP |
443 |
https |
The Robot validates the root certification authority of the code signing certificate. Please notice that this happens only if the root certification authority is not already in the Windows Certificate Store. |
*.nuget.org
|
TCP |
443 |
https |
The Robot downloads the required activity dependencies. |
a23-*-*-*.deploy.static.akamaitechnologies.com
|
TCP |
80 |
http |
The Robot checks whether or not the code signing certificate has been revoked. |
*.service.signalr.net
|
TCP |
443 |
https, wss |
The Robot connects to Orchestrator's SignalR channels. |
*.ingest.sentry.io
|
TCP |
443 |
https |
The UiPath Assistant sends the application errors to Sentry in order to track and solve the most usual problems. |
dc.applicationinsights.azure.com
dc.applicationinsights.microsoft.com
dc.services.visualstudio.com
*.in.applicationinsights.azure.com
|
TCP |
443 |
https |
The Robot uses these endpoints to send telemetry data. |
gallery.uipath.com
marketplace.uipath.com
*.pkgs.visualstudio.com
:information-source: gallery.uipath.com/api/v2 redirects to uipath.pkgs.visualstudio.com
|
TCP |
443 |
https |
These are the URLs for the Marketplace NuGet feed. |
The following actions are performed by the Robot in Orchestrator on packages for these services:
cloud.uipath.com
|
myget.org
|
activate.uipath.com
|
jptk0*.proinity.net
|
*.nuget.org
|
a23-*-*-*.deploy.static.akamaitechnologies.com
| |
---|---|---|---|---|---|---|
Receive |
|
|
|
|
|
|
Send |
|
|
|
|
|
|
Activation |
|
|
|
|
|
|
Not Connected |
|
|
|
|
|
|
Connected from UiRobot |
|
|
|
|
|
|
Publish to Orchestrator |
|
|
|
|
|
|
Manually Start |
|
|
|
|
|
|
Scheduled Start |
|
|
|
|
|
|
Application Update |
|
|
|
|
|
|
Package Update |
|
|
|
|
|
|
Depending on your business policy, some URLs might need to be allowed for the following actions:
- Activating your License - activate.uipath.com (port 443). This URL only needs to be allowed for Robots which are licensed locally.
- Updating Studio - *.uipath.com/beta/ (port 80), Beta update channel for the Community Edition
- Downloading Packages - www.myget.org, *.vo.msecnd.net, www.nuget.org (port 443)
- Connecting to Automation Cloud Orchestrator - https://cloud.uipath.com (port 443)
- Subscribing to Orchestrator's SignalR channels - *.service.signalr.net (port 443)