your server (at least) is configured somehow. probably a .conf file or some such. see which tls level(s) is supports and/or defaults to. i'm pretty sure this error has come up before with okhttputils. try the little search box up at the top of this page. whether you can change okhttputils' tls, i forget. that's why i suggest seeing if you can see what's going on server side. chrome and okhttputils are not the same thing.
i would think if you can successfully connect with some https server in the wild using okhttputils, then the issue is not with okhttputils, right? try
https://www.google.com. i connect with https servers all the time using okhttputils... i just connected to
https://www.google.com with acceptall on.
let me amend that: i've used the okhttputils source modules with the acceptall setting without issue. the handshake issue comes later.