UTM showing GoDaddy certificates as expired, even if they are not

This is really strange. Three things come to my mind while seeing this;

1. Timestamp of UTM9

2. Timestamp of the End machine

3. What is the status of Proxy CA (Signing CA) in the UTM9? You can check that under Webserver Protection > Certificate Management > Certificate Authority.

Hello Jaydeep,

thanks for your Reply.

The answers to your Questions:

1. and 2.: I have checked the time of both the UTM and the client machine. They both get their time from the same GPS NTP source and are within one second of one another.

3.: Our signing CA cert is valid until January 1, 2036 and is present in the cert store of the Client machine.

Other Websites function normally. Only sites with certs from GoDaddy Show this behaviour.

Now that's something when creating a case will help. Please create a support case.

Meanwhile, would you please check the output of these two commands from SSH?

ls /etc/ssl/certs/ | grep Dadd

ls /var/pattern/cadata/ca/ | grep Dadd

This should give a list of the following CA's pem file:

Go_Daddy_Class_2_CA.pem
Go_Daddy_Root_Certificate_Authority_G2.pem
STATIC_GoDaddy.com_Inc_Go_Daddy_Secure_Certification_Authority.pem

Hello Jaydeep!

Output of  "ls /etc/ssl/certs/ | grep Dadd" and "ls /var/pattern/cadata/ca/ | grep Dadd" is identical:

Go_Daddy_Class_2_CA.pem
Go_Daddy_Root_Certificate_Authority_G2.pem
STATIC_GoDaddy.com_Inc_Go_Daddy_Secure_Certification_Authority.pem

Hello Dominik,

Thanks for the update. This is worth a support case.

Hello Jaydeep,

a support Case (#9027832) has been opened.

Thanks for this. I'll keep watching this ticket.

Thanks for this. I'll keep watching this ticket.