Assets Agent is a small application that runs in the background on the same system on which Assets is used. With it, a file can be automatically opened in its native application and checked-in again after editing.
This article describes a scenario when Assets is unable to connect to Assets Agent when using Google Chrome.
Issue
One of the following issues occur:
Issue 1: When trying to connect to Assets Agent by clicking its icon in Assets, a message appears:
(Assets URL) wants to look for and connect to any device on your local network.
When clicking Block, no connection can be made anymore and a notification appears:
Could not connect to Assets Agent
Issue 2: After dismissing the message described in issue 1, it does not reappear, but the notification 'Could not connect to Assets Agent' keeps getting displayed.
Background information
This behavior is related to a security and privacy setting in Google Chrome with which a connection to your local network (such as the connection between Assets and Assets Agent) can be blocked.
Resolution
Step 1. In Google Chrome, access the Local network access settings by entering the following URL:
chrome://settings/content/localNetwork
The middle of the page contains a section for sites that are not allowed to connect to any device on your local network.
Step 2. If the Assets URL is listed there (for example because you clicked on Block), remove it.
The bottom of the page contains a section for adding connections that are allowed to connect to any device on your local network.
Step 3. Click Add and in the dialog that appears, add the main URL of Assets. When done, click Add to close the dialog.
Example: https://assets-documentation.woodwing.cloud/
Step 4. In Assets, click the icon to connect to Assets Agent. It should now be able to connect.
Comments
0 comments