![]() I:/C=IE/O=Baltimore/OU=CyberTrust/CN=Baltimore CyberTrust Root I:/C=US/O=Cloudflare, Inc./CN=Cloudflare Inc ECC CA-3ġ s:/C=US/O=Cloudflare, Inc./CN=Cloudflare Inc ECC CA-3 openssl s_client -connect :443 -servername Ġ s:/C=US/ST=California/L=San Francisco/O=Cloudflare, Inc./CN= Note: the certifi store link in the github text results in 403 error. ![]() If you experience troubles in making clients validate your certificates, we encourage you to disable TLS on your server and privately test them before enabling this feature again We use the certifi store ( link) to validate certificates. In this case, there will be no attempt to establish an unencrypted connection, imitating the behavior of modern browsers. If the client is unable to verify the certificates, it will prevent the connection entirely. NOTE: please ensure that your certificates are valid for your domain name. Did you see this note in the syncplay docs on github? If that's how you have it then the syncplay client will see the Cloudflare cert - not yours (see below). With Cloudflare, usually the client app uses https to connect to the Cloudflare edge and the edge makes another https connection back to the origin server. You may be complicating things by having your syncplay server running behind Cloudflare. Since I'm trying to run a TLS application (syncplay) which uses libopenssl, it will fail too.
0 Comments
Leave a Reply. |