Earlier today a new certificate was deployed for
Issuer: C=BE, O=GlobalSign nv-sa, CN=GlobalSign CloudSSL CA - SHA256 - G3 Validity Not Before: Nov 15 11:18:20 2018 GMT Not After : Sep 7 16:10:08 2019 GMT Subject: C=US, ST=California, L=San Francisco, O=Fastly, Inc., CN=f2.shared.global.fastly.net
It was deployed only a few minutes after the
Not Before time. One of our users had their system clock lagging behind slightly which caused them to receive certificate errors.
Even though this is a user error, I want to suggest backdating certificates if possible, or wait a while until you deploy them after generating them.
Please sign in to leave a comment.