Using Chrome or Edge 136 and higher with Laserfiche Connector may result in an error stating the browser is not configured correctly

May 9, 2025 | KB: 1014571
Laserfiche Connector

Summary

When trying to use an existing Laserfiche Connector profile or when trying to configure a new Laserfiche Connector profile with Chrome or Edge 136 or higher, users may see an error stating:

Chrome is not configured correctly. Follow these instructions to configure Chrome.

New Microsoft Edge is not configured correctly. Follow these instructions to configure new Microsoft Edge.

Cause

Chrome and Edge 136 and higher now require the use of an additional switch, --user-data-dir, to be used in conjunction with --remote-debugging-port. See this post for additional details.

Resolution

Modify the Chrome shortcut target and after

--remote-debugging-port=9222 --remote-allow-origins=localhost

append the --user-data-dir switch. It should now resemble

--remote-debugging-port=9222 --remote-allow-origins=localhost --user-data-dir=C:\MyCustomPath

Modify the Edge shortcut target and after

--remote-debugging-port=9322 --remote-allow-origins=localhost

append the --user-data-dir switch. It should now resemble

--remote-debugging-port=9322 --remote-allow-origins=localhost --user-data-dir=C:\MyCustomPath

Close and reopen Chrome or Edge and Laserfiche Connector after making and saving the change.

The user data directory contains profile data such as history, bookmarks, cookies, etc. Specifying a custom path with the --user-data-dir flag will override the default location of the user data directory and create a new profile, meaning the launched instance of Chrome or Edge will not have any of the settings previously configured for the default profile. Depending on your preferences, you may want to transfer settings over to the custom profile or have two different browser shortcuts, one for use with Laserfiche Connector and another for other web browsing needs.

More Information

See Google documentation discussing the change to the remote debugging switches.

https://developer.chrome.com/blog/remote-debugging-port