Frequently Asked Question

Why can't my Dyostem/Dyostem+ sensor find the server?
Last Updated 4 months ago

Observation:

My Dyostem/Dyostem+ sensor communicates correctly with the server when, in the configuration file, the addresses start with https://www.dyostem.com, but this communication is impossible when addresses begin with http://www.dyostem.com.

Step 1 : Check sensor time and date

To use the secure HTTPS protocol, the sensor asks the server for a certificate and checks it. If the sensor's date is not within the validity dates of the certificate, the certificate is considered invalid and is rejected by the sensor, which cuts off communication with the Dyostem server.
If the date is not correct, change it.

Step 2 : Check that port 443 is not blocked by a firewall

When the sensor communicates with the server using HTTPS (the data exchanged between the sensor and the server is encrypted), it uses port 443 and not port 80. To check whether port 443 is blocked, from a browser on the Dyostem/Dyostem+ sensor, open the page https://www.dyostem.com
If the page is not displayed, contact the IT systems administrator to update the firewall configuration and authorise connection to port 443 on the site. www.dyostem.com.

Please Wait!

Please wait... it will take a second!