How do I set up SSL with HOOPS Communicator using the legacy server?

Part 1: Generate and install self-signed certificate for testing (optional)
Note: This step may be skipped if the user has a supplied key that Is already configured and verified to be working.

  1. Download precompiled Binaries for openSSH if they are not on your system. Windows users may want to use the following URL:
  2. Generate a key and cert file using the following command:
    openssl.exe req -x509 -newkey rsa:2048 -keyout -out -days 365 –nodes

Note: For illustrative purposes, when it asks for FQDN or name, a development machine accessible using the URL matthew-win8.ts3d.lan is used. This will mean that the certificate will work with URLs in the form of ws://matthew-win8.ts3d.lan:<port_num>. We had our IT person create a DNS entry for our developer machine.


  1. To install the cert in chrome (this will also enable the cert in IE/edge) perform the following steps:
  • Go to Settings
  • Show advanced settings…
  • Click on Manage certificates under HTTPS/SSL
  • Click ‘the Trusted Root Certification Authorities’ Tab
  • Click on Import button and select the certificate that was generated above
  • After the certificate is installed, the browser will need to be restarted.


Part 2: Configuring HOOPS Communicator Server to server Secure Websocket data

  1. Launch the settings builder application and chose the mode you desire to configure.
  2. When prompted if IP’s should appear in addresses type: no
  3. When prompted if you need to configure SSL type: yes
  4. When prompted, specify the paths to your key and certificate files.

Reboot the browser after I installed the certificate.

Just a note, that with the release of HOOPS Communicator 2019 SP2, we have deprecated the current server implementation and as such, the above guide will not work for the new server. You can see a note about that in the release notes:

SSL is supported with the new stream cache server just as it was with the legacy stream cache server, but setup has been improved. You can enable use of SSL with your stream cache server instances (which are now launched using ts3d_sc_server instead of sc_server_app) using command line options, which you can read about here:

A complete guide on setup will be provided soon, but in the meantime, if you have questions please reach out to support team or your assigned consulting engineer during evaluation.

Return to