Problem with Minio SSL Hi Jacky,
I have investigated this a little bit.
The issue depends on server and client cipher suites. The same version should be allowed/available on both sides otherwise TLS channel will not be established.
I have look on minio on windows server 2008 installation.
These cipher are availble by default.
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
And these only in case elliptic curve method is used for generating certificate.
TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
If you use self signed ssl certificate, you can regenerate it with elliptic curve method.
Probably you can also ask for such cetificate from the public authority.
Windows 7 client.
We use native client and there is only ECDSA AES-GCM ciphers in common.
No updates available for extending the list.
Browsers (Chrome and Firefox) use ChaCha20-Poly1305 ciphers, that are not included in windows client.
Known workaround for Windows 7 - update minio server certificate.
Windows 10 client
RSA authentication method available, so everything will run smoothly.
Please tell what is your environment (server/client)?
Probably there is an easy way to extend list of ciphers on minio server side, hasn't looked yet.