To me, it looks like there's an issue with the certificate configuration. What process did you go through to configure a CA certificate on the remote server? And to configure a client certificate for Vault to use when calling it? I'd be looking very carefully at those steps.
When we were configuring the certificate on a remote AD instance hosted by Azure, we found it was a bit tricky, at least for us. If you head into your remote instance, open Powershell as an administrator, type the command "ldp", then connect
something.wherever.com/389, and connect
something.wherever.com/636/SSL, do you succeed? Of course, replace those values with your real ones. Also, is the certificate Vault is using a valid identity for one of the CA's that's configured? Once the certificates are correctly configured and have a valid relationship with each other, that error will resolve.