Product Selector

Fusion 5.9
    Fusion 5.9

    Troubleshoot Chrome Binary for Web Connector

    chromeBinaryPath values

    If Google Chrome was installed via package installation manager, specify the Chrome binary in the chromeBinaryPath. Example locations are /usr/bin/google-chrome or /path/to/customlocation/of/google-chrome.

    For RHEL builds, run:

    wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm
yum -y install redhat-lsb libXScrnSaver
yum -y localinstall google-chrome-stable_current_x86_64.rpm

    Then use which google-chrome to find where it installs and use that in the chromeBinaryPath.

    Troubleshooting Chrome binary errors

    Steps to verify:

    • Make sure Chrome is installed properly on the system and google-chrome --version returns successfully.

    • If a custom Chrome binary path is set in the datasource configuration, make sure is it valid.

    • If bundled Chromium is used, where is it located? The Chrome install script puts it inside var/connectors/connectors-classic/chrome-linux, but Fusion looks for it inside var/connectors/connectors-classic/chrome-linux64.

    • Ensure proper permissions are set for the Fusion user.

    • If running Fusion locally, try unchecking the Headless Browser option. This allows Chrome to open to the page = the crawler is indexing and lets you know that Chrome is being reached by Fusion.