I can assume that this is Cisco equipment and it does traffic proxying, it can be a firewall or any network equipment that does proxying and thus replacing the SSL certificate with its own certificate has become obsolete, and you have an error. From the side of our server, we cannot influence this.