ssl_certificate_version disables the requirement for a name-matched certificate (i.e. if you connect to https://1.2.3.4:10200 the certificate must have a name, or subject alternate name, of 1.2.3.4). Setting this is a terrible idea, for reasons that the PDF linked to in the documentation explain.
However, even with a certificate that is not name-matched, there is no reason to allow a TLS connection to use an untrusted certificate when any certificate can be trusted based on either the CA (using the cacert option on the output) or by adding the certificate (including the intermediates, and possibly even the root) to the file pointed at by the truststore option.
If you do not know how to extract the CA or to save a certificate and its intermediates from a website I suggest you take a look at one of the StackExchange sites. I do not know, off the top of my head, which one would be appropriate.