Improvement
Automatic Removal of HSTS Header for "onsite.teramind.io"
This improvement doesn't apply to you if aren't using the onsite.teramind.io domain with your instance.
In TMU 679, we introduced a new certificate scheme. When an instance is configured to work with the onsite.teramind.io address, it will not open by this hostname anymore after the new TMU is installed due to the self-signed certificate and HSTS presence in the HTTPS response header.
Starting from this TMU, the HSTS header will be removed automatically if the onsite.teramind.io certificate is detected, otherwise HSTS header will remain the same.
You can check for the existence of the HSTS header by using the following command:
curl -k --connect-to onsite.teramind.io:443:127.0.0.1:443 -v https://onsite.teramind.io/login
You should receive the following reply if the certificate is NOT for onsite.teramind.io:
strict-transport-security: max-age=63072000; include SubDomains; preload
The browser might cache your previous HSTS settings. To clear the HSTS for the domain follow the instructions in this article.