thanks @wasea for your quick response, i appreciate it.
i did check some prots are open and some are closed, i did inform the network team about those ports before.
the webconfig already put the 8443 port for each node.
another thing please
i run the Orchestrator URL but did not get also any response except the output below from the url: /Account/Login?returnUrl=%2F
{âmessageâ:âAn error has occurred.â,âerrorCodeâ:0,âresourceIdsâ:null}
@JithinKP - the logs refer that the issue is related to the error above
like this one
Blockquote
2020-12-31 05:13:58.6744 UiPath.IdentityServer.Web.Startup An error occurred during initialization of authentication methods
RedisConnectionExceptionIt was not possible to connect to the redis server(s). UnableToConnect on 10.15.61.219:6379/Interactive, Initializing/NotStarted, last: NONE, origin: BeginConnectAsync, outstanding: 0, last-read: 5s ago, last-write: 5s ago, keep-alive: 60s, state: Connecting, mgr: 10 of 10 available, last-heartbeat: never, global: 0s ago, v: 2.0.593.37019 at StackExchange.Redis.ConnectionMultiplexer.ConnectImplAsync(Object configuration, TextWriter log)
at Microsoft.Extensions.Caching.StackExchangeRedis.RedisCache.ConnectAsync(CancellationToken token)
at Microsoft.Extensions.Caching.StackExchangeRedis.RedisCache.GetAndRefreshAsync(String key, Boolean getData, CancellationToken token)
at Microsoft.Extensions.Caching.StackExchangeRedis.RedisCache.GetAsync(String key, CancellationToken token)
at UiPath.IdentityServer.Application.Services.CustomDistributedCache.GetAsync[T](String key, Func`1 factory, CancellationToken token)
at UiPath.IdentityServer.Application.Services.ExternalIdentityProviderService.GetPartitionActiveIdpsAsync(Partition partition)
at UiPath.IdentityServer.Application.Services.ExternalIdentityProviderService.GetHostPartitionActiveExternalIdentityProvidersAsync()
at UiPath.IdentityServer.Web.Extensions.Configuration.ExternalAuthenticationMethodsExtension.AddAuthenticationMethodsAsync(AuthenticationBuilder builder, IServiceProvider serviceProvider, AppSettings appSettings)
@m_altourky - I donât think itâs a bug. I did set up HAA twice and it was smooth (didnât have to worry about pre-requisites though). We are missing something here. Only difference I can see is you are trying 2019 version and there may be some changes in 2020 version but that shouldnât be a concern I guess. Let me see if I can try 2019 in Azure.
i tried every possible ports 10000,36379,6379
still getting the orchestrator error
{âmessageâ:âAn error has occurred.â,âerrorCodeâ:0,âresourceIdsâ:null}
there was error on opining the /identity/ url
but when editing the C:\Program Files (x86)\UiPath\Orchestrator\Identity\appsettings.Production.json
and change the ports from 6379 to 10000 it worked on the /identity/ url and strart to ask for credentials. but not the orchastrator.
@m_altourky - Is HAA up now? Through Identity also you are not able to access orchestrator? Will you be able to check event viewer for that Orchestrator error?
Instead of us going through errors one by one, lets get UiPath Technical Support. It will save time and effort, hope you have an Enterprise Key for Orchestrator?
@Nic_Surpatanu thank you for your time, the issue is am stuck with the first node of orchestrator so still the other node not installed yet as i am facing this error with the primary server.
@m_altourky Did you restart the website after you made config changes? It seems the config is not picked up. What is the error you have in event log after you restart and try to connect to Orch? Set the Orch diagnostics logging to Trace and take a look what is going on.
Dear @Nic_Surpatanu,
every time i made change to file inside the orchestrator directory i restart the IIS and make iisreset using command line as administrator sometimes.
First of all, you need to be sure that you use the correct port for HAA. Based on our official documentation, HAA uses port 10000 by default & 10000-19999 is the port range for database traffic. I suggest to use 10000 port. Based on your last provided logs, port 36379 is used
After that, you need to be sure that BOTH Orchestrator & Identity config files are updated:
Do you still have an error after you set the settings? If yes, please provide us the Event Viewer logs from the Orchestrator machine in order to debug them.
@Nic_Surpatanu, @JithinKP, @wasea, @rocsana thank you all for every thing i will reset all servers to default state and try to install All product again.
i did - as i mentioned early - use all ports in both setting files starting with 6379, 36379, 10000 with the last port number the only thing works is the /identity/ url.
i am now working on all servers again from scratch, so thank you for your time and support, i really appreciate it.