Hi All,
Good day!
I have an attedlnded automation. When deployed in the user machines. When run through the UiPath assistant, the bot failed with error message “cannot communicate with browser .”
Upon checking the user’s machine, we found that the UiPath extension were disabled and toggle is greyed out.
The work around I did, is to manually created new chrome profile and enable the UiPath chrome extension.( Not ideal solution when there are large number of bot users)
Therefore it would be great if anyone can help me find a permanent solution for the same.
Thanks & Regards,
Jennish
Hi @gurumayum.sharma
it’s usually due to chrome policies or corrupted profiles. Try to deploy and enforce UiPath extension via group policy or enterprise management tools.
If helpful, mark as solution. Happy automation with UiPath
@gurumayum.sharma,
This is generated by Forum bot and I think should work in your case.
Based on the issue and available documentation, a permanent solution is to deploy the UiPath Chrome extension via Group Policy rather than relying on user-specific profiles. In an enterprise environment, you can configure Chrome’s policies to force-install the extension, ensuring that it is enabled (and not greyed out) on all user machines.
Here are the key points:
- Force-Installation via Group Policy:
Use the Chrome Group Policy setting “ExtensionInstallForcelist.” This policy forces Chrome to install certain extensions. For example, on Windows machines that are joined to an Active Directory domain (offline installation), you would add an entry with the UiPath extension ID along with the local path to the extension manifest. The documentation states that for AD-joined machines, your policy value should look like:
•
ndmegdjihnhfmljjoaiimbipfhodnbgf;file:///C:/ProgramData/UiPath/UiPath.Common/ChromeExtension_SelfHosted/extension_manifest_chrome.xml
For machines that are not joined to AD (online installation), use:
•
kmejkhcmhgilmppjodlgaklnmdmmhhcl;https://clients2.google.com/service/update2/crx
- Additional Policies:
- DeveloperToolsAvailability: If the extension is installed using Group Policy, this setting must be set to 1 (allowing the usage of Developer Tools) so that the full extension functionality is available.
- Also, ensure that policies such as NativeMessagingBlocklist, ExtensionInstallBlocklist, NativeMessagingUserLevelHosts, BlockExternalExtensions, ExtensionAllowedTypes, and ExtensionSettings are set correctly so that they do not inadvertently block or limit the functionality of the UiPath extension.
- References:
You can find these details outlined in the UiPath documentation for Chrome Group Policies. For example, the UiPath Studio Group Policies documentation explains how to configure these settings and get the extension properly installed across your organization.
By configuring and deploying the UiPath Chrome extension via Group Policy, you ensure that every user machine automatically installs and enables the extension without requiring manual intervention or profile changes. This approach scales well for large bot deployments.
Make sure to test the policy settings on a few machines before rolling them out across the organization to ensure that no other policies interfere with the proper installation and functioning of the extension.
Hi @gurumayum.sharma
Kindly coordinate with your IT team to enable the extension. If you are connecting from your office laptop - I believe only the admins will have the rights to reinstall with group policy enabled
Also - You can confirm that it is disabled by closing all the browser after making below changes and try again
Extensions → Manage Extensions → Allow in InPrivate, Allow access to File URL’s, Collect Errors
Thanks @ashokkarale will check on this and let you know.
Thanks @sharazkm32
I will check on this and update you.
1 Like
