UIPath Orchestrator Installed but not able to connect

Hi, I have installed UIPath Orchestrator with all the prerequisites. But I am not able to connect to Orchestrator. I am getting the below error.

IDX20803: Unable to obtain configuration from: ‘[PII is hidden. For more details, see Bing]’.System.InvalidOperationException: IDX20803: Unable to obtain configuration from: ‘[PII is hidden. For more details, see Bing]’.
at async Task Microsoft.IdentityModel.Protocols.ConfigurationManager.GetConfigurationAsync(CancellationToken cancel)
at async Task Microsoft.Owin.Security.OpenIdConnect.OpenIdConnectAuthenticationHandler.ApplyResponseChallengeAsync()
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationHandler.ApplyResponseCoreAsync()
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationHandler.ApplyResponseAsync()
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationHandler.TeardownAsync()
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContextStage.RunApp(Func<IDictionary<string, object>, Task> entryPoint, IDictionary<string, object> environment, TaskCompletionSource tcs, StageAsyncResult result)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task Microsoft.Owin.Security.Infrastructure.AuthenticationMiddleware.Invoke(IOwinContext context)
at async Task UiPath.Orchestrator.Web.Owin.GlobalExceptionMiddleware.Invoke(IOwinContext context)

If anyone faced this issue and got resolved. Please give some helpful pointers.

Hello @Ganesh_Karri!

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.

  5. Meet us and our users on our Community Slack and ask your question there.

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

A little late to the party on this one…

I just ran into this while configuring a secondary Orchestrator Node along with HAA / Redis. We upgraded from 2019 to 2020, but had not been using the secondary node yet.

In testing once HAA was setup, I confirmed Node 1 was working, but when I disabled Node 1 and enabled Node 2 I ran into the error you described.

Which led me to the following document

To enable the logging of sensitive information such as certificate public keys or hidden PII (personally identifiable information), update the following setting in the Identity Server’s appsettings.Production.json file, within your existing AppSettings section:

JSON

"AppSettings": {
   "EnablePII": true
 },

In my case, I did not need to adjust the setting to determine the issue as I could see some old information that didn’t update from 2019 configuration. (RedisConnectionString was pointing to defunct servers and UseRedis was set to True. (I had not gotten around to configuring Identity with Redis yet.

I would look over the appsettings.Production.json configuration file to ensure your settings are correct along with the certificate used by the Identity Server, etc.