Generated by LLM
The “Could not connect to SignalR” error in UiPath Studio Web typically occurs when there is a connectivity issue between UiPath Studio Web and the orchestrator, which uses SignalR to communicate between components. To resolve this issue, here are some steps you can follow:
- Check Network and Firewall Settings
- Ensure your network is stable and that there are no restrictions that could block the communication between UiPath Studio Web and the Orchestrator.
- SignalR communication may be blocked by firewalls, proxies, or other network security measures. Ensure that ports required by UiPath are open.
- Make sure that
443(HTTPS port) is open for communication between the Studio and the Orchestrator.
- Verify Orchestrator URL
- Ensure that the Orchestrator URL configured in your UiPath Studio Web is correct. If you’re using a cloud Orchestrator, make sure the URL matches exactly.
- If you’re using a private Orchestrator, ensure it’s accessible.
- Clear Browser Cache
- Sometimes, browser cache can cause issues with connectivity. Clear your browser cache and try again.
- Alternatively, try opening UiPath Studio Web in a different browser to see if the issue persists.