NX selft signed certificate is changing
AnsweredHello there,
I hope you all are doing well.
Because of Chrome security we must to add the NX Certificate to the "Trusted root certification" to can access without warnings like invalid certificate. We realize that certificate is changing after a interval of time (we don't know how much) and this prevent certificate match with the previously certificate added in the "Trusted root".
Also after including the certificate to the Trusted root, Chrome do not stop of blocking our connections to our NX server. This is the message:
XX.XX.XX.XX normally uses encryption to protect your information. When Chrome tried to connect to XX.XX.XX.XX this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be XX.XX.XX.XX, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit XX.XX.XX.XX right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
This is a big problem because cannot avoid the warning using our DNS and adding the certificate to the trusted root.
We know about bypass it using "thisisunsafe" words on Chrome (it works, we tested it) but is not a solution for us.
Thanks
-
Hi Miguel Dina,
If you've already added the Trusted root to your computer, maybe you could refer to the article here to clear some cache files of your browser. It seems that the problem is related to your browser or computer.
Actually, a permanent solution is to apply for a valid certificate that is issued by the certificate authority. So that you don't need to worry about the change of Nx self-signed certificate anymore (but you should renew the server certificate periodically still). See the article to know how to add a custom certificate for the Nx server.
Let me know if you have further questions, thank you.0
Please sign in to leave a comment.
Comments
1 comment