Steiger Posted February 1, 2018 Posted February 1, 2018 (edited) Hi There We updated our Thawte certificate and applied the update to our dedicated pulseway server. We have a 2008 server that goes offline when applying the new cert, when we switch back to the old cert the server comes back online. We have an environment with over 70 Servers and this Windows 2008 enterprise server is the only one that gives us the following error when validating its credentials. Please advise what steps to follow? We have checked time and date settings, ensured machine is up to date. All the best, Thomas Edited February 1, 2018 by Steiger
Staff Chris Posted February 1, 2018 Staff Posted February 1, 2018 Hi Thomas, It is possible that some of the root certificates are missing on your system. Please open the URL using the internet browser and check it.
Steiger Posted February 1, 2018 Author Posted February 1, 2018 Hi Chris I've checked and they're all there. Its strange how its only affecting this one server Thank you for the help
Staff Chris Posted February 1, 2018 Staff Posted February 1, 2018 In that case, is it possible that you have enabled only TLS 1.2 encryption protocol on this system? If yes, then you will need to enable TLS 1.2 for .NET framework, by running built-in script 'Enable TLS 1.2 in .NET Framework 4.0' on this system.
Steiger Posted February 1, 2018 Author Posted February 1, 2018 Hi Chris Thank you for the information. It would seem the older Cert we were using was compatible with .Net 4 but the new certs being issued support .Net 4.5 and above TLS 1.1/1.2 and above. As this is production machine ill have to schedule a .net upgrade which should resolve the issue. Will revert back with the outcome to help others experiencing this issue.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now