Knowledge Base

Certificate Preparation

If the customer has the PFX format certificate, KEY and CRT format files should be extracted from PFX format. This can be done, using:

• DigiCert Certificate Utility for Windows (GUI tool, easy to use)
  https://www.digicert.com/support/tools/certificate-utility-for-windows
• OpenSSL tool (command line tool)
  openssl pkcs12 -in server_address.pfx -clcerts -nokeys -out server_address.crt
openssl pkcs12 -in server_address.pfx -nocerts -out server_address.encrypted-key
openssl rsa -in server_address.encrypted-key -out server_address.key

If the customer has the certificate and key in KEY and CRT files, the PFX format file should be created. This can be done, using:

• OpenSSL tool (command line tool)
  openssl pkcs12 -export -out server_address.pfx -inkey server_address.key -in server_address.crt

A new password will be asked during this process which should be added to the .env file (as CERT_PASSWORD).

Docker Container Name Resolution

After starting NoldusHub, the docker containers were not able to communicate/ping each other via container name.

Example: In the noldus-hub-api container, the ping rabbitmq command failed (request could not find host).

Solution:

• The Windows Defender profiles were Domain controlled (which overtook some network settings).
• Every Windows Defender Firewall Profile on the Local GPO was changed to off:
  Local Security Policy / Security Settings / Windows Defender Firewall with Advanced Security
  Set every profile (Domain, Private, Public) to off (from not configured).
• Additionally, some security products (e.g. CrowdStrike) can block the network communication.

Checking Server Port Access from Participant PC

On the customer computer infrastructure, security products like extra firewalls might be applied. These can block the network communication between the server and Participant PC.

Example: The Test-NetConnection (PowerShell) command was used from the Participant PC to connect to a server port. The command showed the TcpTestSucceeded result as true, but as soon as the connection was built up, a firewall immediately blocked and refused the communication. This problem was difficult to detect because the connection test passed.

Solution: Disable the additional blocking firewall.

Video Streams

If the webcam image is not available or it appears as black, check the Imaging devices (or USB devices) in Device Manager. Only one webcam must be enabled. Disable all but one and restart the NoldusMedia plugin.

If the video streams are still not available with the MediaPlugin, use the Caller page from a Chrome browser as a temporary solution. Possible causes:

• One of the security software products might block the WebRTC connection with the NoldusMedia plugin.
• The network/firewall settings.

Shimmer

• If the Participant computer is a PC (not a laptop), the USB Bluetooth dongle must be on site at the installation time.
• The dongle driver should be updated before the installation process.
• If the EDA data does not appear, check the device frequency settings (GSR+ 128 Hz; ECG 512 Hz).

Problems with Connectivity

If a Shimmer device has problems with Bluetooth connectivity, it is possible that some security software on the Participant PC is blocking that. This has been observed at the customer with Windows 10 OS and GSR+ device.

Symptoms:

• It is hard to get the device connected (and streaming) to the Consensys Tray app. This usually works better if the device is placed in the dock.
• If the device is removed from the dock while connected and streaming, the connection is lost after a couple of minutes. Consensys Tray app shows "Connection Lost" status. After that, it is very hard to get the device to stream data again.

Mitigation:

• Test the same Shimmer device with another computer without any security products (except Windows Defender).
• Re-flash Shimmer device firmware. Make sure to erase existing configuration. Note: after that, this device will need to be configured properly (see the points above).
• Note: When it is not possible to connect to Shimmer via Bluetooth, launch Consensys, select the device and make it stream to PC.
• Use internal Bluetooth (PCIe) rather than an external USB Bluetooth device.

Tobii Eyetracker

The eye tracker position in Tobii Manager software must be set up correctly before using it from the N-Linx Plugin. Without a working setup, the plugin cannot send any eye tracking information, or only very limited information.

Eyetech Eyetracker

Eyetech eye trackers do not come with setup software. Instead, only a driver needs to be installed, and the correctly versioned Eyetech NLinx plugin needs to be used. It was observed upon several occasions that after installation of a newly unboxed Eyetech eye tracker on a cleanly installed system, the eye tracker could not be calibrated, and the gaze overlay was fixed at the (0,0) position (top left side of the screen capture window). In addition, the gaze projection did not respond to the gaze of the person in front of the eye tracker, although the eye tracker did detect both eyes (indicated by both green lights in the eye tracker).

This failing gaze detection was the result of missing calibration information. As long as there was no successful calibration made, the gaze position remained at (0,0). To overcome failing calibrations, the eye tracker needed to be positioned exactly below the screen, with the right angle and distance to the subject. Only then did calibration succeed, and calibration info could be used to calculate actual gaze positions.

Verify Installation Requirements

NoldusHub versions 1.6 and up require an SSL certificate to be installed on the server.

Installation Readiness Tool

The Installation Readiness Tool helps verify whether a system is prepared for installation by checking if it meets the required criteria. This tool is a single PowerShell script and is regularly updated with new checks and improvements as part of ongoing development.

Distribution

The Installation Readiness PowerShell script is distributed together with the NoldusHub installation package (in a separate directory).

Source: NoldusHub 1.7 Installation Documentation, Noldus Information Technology