I am creating an Azure pipeline but getting the same error with all the 3 types of connection authentication. Pipeline is unable execute ‘UiPath Deploy’ Task. I am facing the same issue using both local host agent and Azure Pipeline agent.
This is the error:
Failed to run the command. Could not connect to Cloud Orchestrator: https://cloud.uipath.com/, Account Name For App: ***, Application Id: ***, Application Scope(s): ***, Tenant: , Organization Unit: Shared.
Please make sure that the provided URL (https://cloud.uipath.com/) is correct, available from your build agent, and not blocked by a firewall.
If the Orchestrator is using a self-signed SSL certificate, make sure that the build agent trusts it. Ensure that all the steps at https://docs.uipath.com/orchestrator/docs/self-signed-certificates were correctly followed when creating the certificate.
My Agent is a local host (my laptop). I can see the project’s NuGet package and the process itself being deployed on my laptop, but I am still not able to deploy the package to the orchestrator using UiPath Deploy Task on the release pipeline.
we were just asking in this direction, as this week we struggled with Pipeline and the “Could not connect…”… which can have several root causes but finally was solved by us
Exactly on the Service Connection (e.g. External App) older Tutorials, Screenshots did show a procedure which results to fail.
So feel free to share with us details
Orchestrator type, Connection authentication, settings etc.
Whenever any connection was workin in the past then focus on the step and YAML definition (we observed on a second case of a second person on other environment)
first try to go to the Market place–>Browser market place–>search for UiPath–>install UiPath integration–>go back and check the in azure.Hope this might help you @Ayush_Raj.
