That's strange, the certificate should be valid (from Let's Encrypt, SHA-256 fingerprint ending in …ccdb4). Could it be an issue with client time settings or an outdated browser cache?