...
As a troubleshooting step, site administrators can confirm that the web socket connection is active while the Agent is running by visiting https://localhost:8070/ssl in a web browser. The confirmation of an ‘Ok’ ‘OK’ message in the browser window will indicate that the Agent is running properly and able to send/receive communications.
After that, further troubleshooting steps can be taken on the local PC to review network and firewall configurations, ultimately to determine if communications inbound/outbound are allowed on that port via the Agent.
Browser Extension Conflicts
Users may have browser extensions installed that interfere with communications that must take place between ClinSpark/Agent for interface workflows. More details on browser extensions are here: https://foundryhealth.atlassian.net/wiki/spaces/DOCS/pages/3700260899/Overview#Browser-Extensions
If users are unable to invoke device workflows, they should check to see if extensions are part of the cause. Using Chrome Developer tools for example, errors like the following may be present in the console:
...
In this example, a browser extension is blocking interactions between browser and the Agent, forcibly closing connections. This is accompanied by this message in ClinSpark:
...
This condition is symptomatic of ClinSpark being unable to communicate with the Agent on the local PC.
This is observed with browser features/extensions that enforce wide-spectrum content blockers (like uBlock, AdBlock, etc). Additionally, certain endpoint protection services that enterprise IT enforce on site machines may also cause this.
Device Dependencies on Visual C++ Runtime 2013
...