Re: [go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

For history: we've made it work with Let's Encrypt issued certificates too: adding *ForceRSA: true* to autocert.Manager did the trick. четверг, 9 февраля 2017 г., 10:48:08 UTC+3 пользователь Alexandr Emelin написал: > > Just tried trial certificate from Comodo - it works! So the problem is in

Re: [go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

Just tried trial certificate from Comodo - it works! So the problem is in Let's Encrypt issued certs. Having such a workaround solves my issue, many thanks for pointing me in right direction guys! среда, 8 февраля 2017 г., 21:09:00 UTC+3 пользователь cynexit.x написал: > > On 02/05/2017 09:44

Re: [go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

On 02/05/2017 09:44 AM, Alexandr Emelin wrote: > Chrome 49 on Windows XP SP3 Are you using a cert from let's encrypt? There have been issues in the past (although LE officially lists Windows XP with SP3 as supported), check these links out: https://github.com/certbot/certbot/issues/1660

[go-nuts] Handshake failed when using builtin TLS package: no cipher suite supported by both client and server

When using builtin TLS for http/websocket server I noticed that handshakes from some old browser clients fail. The reason why I find this strange is that other TLS implementations work with those connections without any problems. I used ssllabs.com/ssltest/ to