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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
BAD CERTIFICATE with consul connect #16617
Comments
Found a workaround, with this topic: Discuss Hashicorp In consul config:
But, I don't really understand if exists a solution for Consul 1.15+ Thanks |
After many tries. No more functionnal. I tried to create a separate CA and cert.
Error message change! 馃コ Now I have:
馃槩 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi 馃憢馃徎
Overview of the Issue
I tried to create hashistack with ACL and TLS on single node for now.
When I launch a test job with consul connect won't work
I posted issue here after this thread on discuss: Nomad discuss after it is advised to post on Consul forum.
Consul 1.15.1
Nomad 1.5
I see in changes what it needed to work. But I don't know how to apply with Nomad job deploy.
I'm not sure about which from Consul or Nomad come from issue
Reproduction Steps
Create a single node Hashistack with Consul 1.15.1 Vault 1.13 (consul backend) Nomad 1.5 .
Launch job with first Sidecar:
and second job to connect to sidecar:
Consul info for both Client and Server
Consul Info:
Client and Server HCL config (single node)
According to this docs: Nomad Consul Connect integration
Nomad conf:
Operating system and Environment details
Ubuntu 22.04 (in VM for testing)
Log Fragments
In Nomad UI:
I created certs with openssl and ansible. It works. Without launch job, I have no error in communications between each components of Hashistack.
Help! 馃啒
The text was updated successfully, but these errors were encountered: