Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to use client tls certificates always results in 'remote error: bad certificate' #59

Closed
alvaroaleman opened this issue Nov 18, 2016 · 1 comment

Comments

@alvaroaleman
Copy link

alvaroaleman commented Nov 18, 2016

Hello,

I am trying to use consul-replicate on a TLS-enabled consul, command looks like this:

CERT=/path/to/crt
KEY=/path/to/key
CONSULHOST=127.0.0.1:8500
consul-replicate -consul $CONSULHOST -ssl -ssl-cert $CERT -ssl-key $KEY -ssl-verify=false -prefix="key@my-dc"

This results in a remote error: bad certificate. However, both a curl -k $CONSULHOST --cert $CERT --key $KEY and a consul-template daemon using the same ssl-opts work fine, so this looks like a bug in consul-replicate to me.

alvaroaleman added a commit to alvaroaleman/consul-replicate that referenced this issue Nov 18, 2016
alvaroaleman added a commit to alvaroaleman/consul-replicate that referenced this issue Nov 18, 2016
@alvaroaleman
Copy link
Author

For future reference: This didn't work because those configurations options were present but did not do anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant