How to unblock the launching of Connect 3.6.5+ in Chrome

Issue

While at a website that makes use of the Aspera Connect Browser Plug-In, Connect fails to launch and a blue banner is shown prompting you to download the latest version. This occurs even when you have the latest version installed.

If you view your browser console, you may also see an error message like the following:

https://local.connectme.us:43003/v5/connect/info/ping Failed to load resource: net::ERR_CONNECTION_REFUSED

This problem is most likely due to a browser setting that prevents Connect from launching.

Environment

  • Product: Connect Browser Plug-In
  • Version: 3.6.5+
  • Browser: Chrome

Solution

On Chrome, you usually receive a pop up window when attempting to use Connect that asks you to allow Connect to launch:


If you click Do Nothing, Connect will fail to launch. Refreshing the page should prompt you to allow Connect to launch again.

However, if you click Do Nothing and select the Remember my choice for all links of this type, you will need to make a file modification in order to unblock Connect.

1. Close the Chrome browser

2. Open the Local State file at the following location:

  • Linux:  ~/.config/google-chrome/Local State
  • Mac: ~/Library/Application Support/Google/Chrome/Local State
  • Windows: C:\Users\user\AppData\Local\Google\Chrome\User Data\Local State

3. Find the protocol_handler object. In excluded_schemes, you will find a setting for fasp which is set to true:

"protocol_handler":{
  "excluded_schemes":{
     …
     "fasp":true, ## remove this or set to false ##
     …
  }
}

This setting configures Chrome to block Connect from launching. You can either remove this line entirely to have Chrome prompt you with the request window, or you can change the value to false to always allow Connect to launch.

4. Save the file and reopen Chrome. Connect should now be able to launch on Connect-enabled sites.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk