Cannot log into orchestrator. Username and password prompt not appearing

Help Orchestrator
1

We are unable to log into our UAT orchestrator as the username and password prompts are not appearing.

We are not having the same difficulties with our Production orchestrator.

We have tested both the UAT SQL and UAT Application servers and there is no issues with these. They can ping each other with very short delays (2 or 3 ms).

We have looked at the json files for both the UAT and Production environment and they seem to match exactly except for the required URL and license keys specific to each environment.

The SSL cert for the UAT environment is also well in scope. Scope and binding the SSL certs are all in order.

Any advice on what we can check, or if you have found a fix would be very much appreciated.

Regards

John

2

Hi @john_odonoghue

Have you tried deleting the browser cookies and then reloading browser to login?

Also, may be try login from another browser like edge if you are using chrome at the moment.

Could you please confirm if you are not able to login to UAt orchestrator from any machine? or is it just specific to some machines?

3

Hello Sonali

I have deleted all cookies in Chrome but the problems remains.

In addition I tried with Edge, but the log in problem is exactly the same.

We cannot log into the UAT orchestrator from any machine and this is true for all users who attempt to do so.

In addition, if we try to run a robot (from Studio) that accesses assets stored in UAT Orchestrator, it cannot access those assets.

Regards

John

4

Hi @john_odonoghue

Please check firewall might be blocking or any proxy issue. if not Pls raise a support ticket to UiPath .

Happy Automation

5

Hi @john_odonoghue

Thanks for confirming.

looks like orchestrator connection is not there even via assistant.

Could you please confirm how are your assistant/studio connected to orchestrator? Is it via sign-in? if yes, please note you wont be able to access anything from orchestrator unless you are able to sign in manually as well to orchestrator.

if you are connected via machine key, you might be able to get through.

So, for this, I would suggest:

  1. Please raise a support ticket to UiPath on same. Also, raise a ticket internally to your network services team to check if any firewall or anything might be preventing the connection.

Also, please confirm your orchestrator setup. Do you guys have separate tenants(uat/prod) on the same site?
Or you guys have separate sites itself for uat and prod?

Also, are you guys on on-prem or cloud version and what version you guys are on?

6

Hi all,

Problem solved. It turns out there were updated certs in IIS, but out UiPath installation was still looking for the older certs. Once we updated the JSON files, our UAT Orchestrator started working again.

BTW in answer to your question, we are fully on-prem. I know we have to enter very different URL addresses for UAT and Production so I suspect they are on separate tenants, but I also suspect they may be on the same site.

Thanks for all the suggestions.

John O’Donoghue

1 Like
7

@john_odonoghue

Glad to hear your issue is resolved.

Please mark your last post as solution so this topic can be closed and help others with similar issues.

8

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.