UiPath studio & UiAssistant Sign In button is not responding (not redirecting to website).
When I click Sign In button it goes gray to blue without responding anything.
Note: I have only 1 browser in my laptop which is a default app.
What I Tried & still not worked:
Opened url cloud.uipath.com and tried clicked Sign In button but is still not working.
Uninstalled and again Installed UiPath Studio.
Already a browser (msedge) is a default browser and only 1 browser in my laptop.
Restart my pc.
What wrong with this? can anyone resolve this issue ?
Go to Orchestrator Settings. If there is a connection already, Disconnect it. It should end up looking like this:- (If there is an Orchestrator URL already pasted, click the delete button on the right side)
Now paste the Orchestrator URL and the Machine Key. If you don’t have the key, Go to your tenant in orchestrator and create a machine template with a robot account, you will get a machine key. (I’ll try to attach the documentation for it)
Click Connect. After successful connection, it should look like the below Screenshot (automatically signed in). If you see a Sign In button instead of a Sign out, Just click the sign in. It should ideally take you to the browser and log in.
Ensure Edge Browser is not opening in the background. Click on Task Manager and End Task all browser related activities.
Also Check Edge Browser Settings from the url edge://settings/defaultBrowser
Ensure that “Let Internet Explorer open sites in Microsoft Edge” is set to “Always”
Ensure that “Allow sites to be reloaded in Internet Explorer mode” is disabled.
Restart Edge and give a try
Try via CMD to see if it is working or not. Share the result here
Open CMD and enter the command - start https://cloud.uipath.com
Are you connecting from home or office network? Any possibility for firewall issue?
Try resetting UiPath settings
Navigate to C:\Users\YourName\AppData\Local
Delete or rename the folder UiPath
Restart the system and open Studio Sign IN
Check Edge Pop-up Blocker
Go to Edge Settings → Cookies and site permissions → Pop-ups and redirects.
We had a similar issue last year and discovered the following regarding our proxy settings:
There was a change .NET Core and .NET 5+ to make the platform more agnostic.
Environment variables http_proxy and https_proxy are now primary and relied upon, instead of WinINet APIs.
When http_proxy and https_proxy are not defined, .NET will lookup the proxy settings defined for the individual user.
Proxy settings must explicitly set HTTPS either in environment variable https_proxy or within the User Proxy Settings, otherwise WinINET will default to HTTP.
When the “Sign In” button is not working it is a good sign that the request is not being sent via HTTPS. Let us know if the information above helps resolve the issue you are experiencing or if the issue persists along with user proxy settings and/or https_proxy environment value.
How I resolved this issue? → Just changed the WIFI network. Sign In button was not working in my home network, so I connected my Neighbour WIFI, and it worked.