After this particular partner's api changed it's ssl certificate to a Global Sign Let's Encrypt one all the customers that use Windows Server 2012 R2 have been experiencing 12029 (-1) error code.
Some parts of the internt say that if you update windows enough you would solve the issue, but instead what I did was to change the HttpConnectionType to indy. It solved the issue.
While debuggin on wireshark i've found that the problem happens on the handshake step.

I'm just posting this here because I was not able to find a alternative solution or even someone else talking about. I know that this is a Windows issue.