I am not 100% certain as to the cause, but I have also seen this issue, and I ended up with "brute force" troubleshooting: read the logs and try to make anything that I think is "weird" go away.
While the logs indicate that there are some SSL "errors," but that those are accepted, the connection gets aborted, so I started to see if I could make some of those errors disappear.
My first step (toward anything fruitful, at least) was to fire up IE and hit the IP address of my consoleproxy:
https://<consoleproxyIP>
I accepted the warning about a questionable certificate and connected to the site anyway.
From there, I looked at the certificate and clicked the "Install Certificate" button. Based on a couple of the warnings, I decided to put the self-signed certificate into the Trusted Roots store on my client (probably not good for production environments -- you should be using real certificates issued by a real CA -- but it works for test/dev).
I restarted my browser and tried again -- my console connected fine and the log file indicated that I had eliminated 3 of the warnings, including the two "untrusted chain" errors (as expected) and the "134217857" warning ... no idea what that one's all about.
Worth a shot?