orchestrator
latest
false
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide
Last updated Sep 17, 2025
General troubleshooting
linkThe remote certificate is invalid because of errors in the certificate chain: UntrustedRoot
linkThe
net::ERR_CERT_AUTHORITY_INVALID
error occurs when your certificate expires or is involved in a certificate rotation process, indicating that it is now invalid.
It is most likely that the error occurs for the following reasons:
-
You cannot access Automation CloudTM.
-
Your robot is disconnected.
Figure 1. Your connection is not private warning
Figure 2. UiPath Error message
To fix this error, take the steps, described in the following example:
- In a browser window, navigate to Automation CloudTM via
https://cloud.uipath.com
. - Select the Not secure warning prompt. Then select Certificate is not valid from the dropdown menu.Figure 3. Certificate is not valid warning
- In the Certificate Viewer, select the Details tab. Then select Export and save the certificate.Figure 4. Details tab
- On your local machine, open certlm.msc and right-select the Personal folder, then select All Tasks, then select Import. Select the previously generated certificate and import it.Figure 5. Importing certificate
- In the same certlm.msc window from the previous step, select the Trusted Root Certification Authorities folder, then select All tasks, then select Import. Select the previously generated certificate and import it again.Figure 6. Importing certificate
- Connect the robot again to check that the error is fixed.Select the View site information icon. Select Connection is secure from the dropdown menu.
Browser group policies
linkSigning in to your Orchestrator service from the Assistant redirects you to the SSO page. In some browsers, you may be prompted to open UiPath Assistant. This happens due to the Assistant's protocol handler not being added to the browser's group policies.
To prevent this behavior, make sure to follow the next steps, depending on the browser (Chrome/Microsoft Edge):
- Open Registry Editor.
- Navigate to
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
/ orComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge
, depending on the browser you use. - Add a new key and name it
AutoLaunchProtocolsFromOrigins
. - Select (Default) to edit the key.
- In the Edit String dialog, in the Value data field, add
[{"allowed_origins": ["<https://myOrchestrator.uipath.com/"],"protocol":> "com.uipath.robot.oidc"}]
and select OK.Important: TheAutoLaunchProtocolsFromOrigins
policy requires Chrome 85 or later. - Close all browser tabs and relaunch the browser.
- Verify that your browser applied the new policy by navigating to
chrome://policy
oredge://policy
. The recently added policy should be listed under the Chrome Policies or Microsoft Edge section with the OK status.