Comment 1 for bug 1292202

So i've tried this setup with both installing certificates manually and with ssl_setup and the behaviour of --insecure/--os-cacert works for me with both.

The curl command appears to be going to the correct endpoints which is always my first guess. Don't worry about the fact the curl statement is missing the certificate files - that is a debugging statement only.

In curl -k is --insecure, i'm not sure if that's a mistake in the bug report or your curl command is also doing an insecure connection. That would help explain it if it's not.

Other things to check when setting up ssl, you should set:

[ssl]
cert_subject=/C=US/ST=Unset/L=Unset/O=Unset/CN=172.16.12.49

if you are going to use ssl_setup so that the hostname is correct.