Jump to content

Pulseway/Windows Server 2008 Enterprise SSL/TLS Relationship Error


Recommended Posts

Posted (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.

image.png.38c55e4c8d371ec021d36ca44801cb4a.png

 

Please advise what steps to follow?

We have checked time and date settings, ensured machine is up to date.

All the best,

Thomas

 

Edited by Steiger
  • Staff
Posted

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.

image.png.ff8e9e9ccf3b8ef1092e37490ce0aafe.png

Posted

Hi Chris

I've checked and they're all there. Its strange how its only affecting this one server

image.png.29eeab82d5bc33979a88592814240d07.png

Thank you for the help

  • Staff
Posted

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.

Posted

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.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...