You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @pellepelster! It looks like you're using Consul with TLS?
We have a report of this in #6594 and an issue to work through the testing for it in #6502. So I'm going to close this one as a duplicate but thanks for reporting it!
Fixes#6594#6711#6714#7567
e2e testing is still TBD in #6502
Before, we only passed the Nomad agent's configured Consul HTTP
address onto the `consul connect envoy ...` bootstrap command.
This meant any Consul setup with TLS enabled would not work with
Nomad's Connect integration.
This change now sets CLI args and Environment Variables for
configuring TLS options for communicating with Consul when doing
the envoy bootstrap, as described in
https://www.consul.io/docs/commands/connect/envoy.html#usage
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Nomad version
0.10.1
Operating system and Environment details
Debian GNU Linux 9
Issue
Following the guide from https://www.hashicorp.com/blog/consul-connect-integration-in-hashicorp-nomad/ the created sidecar services in consul show failing healthchecks
dial tcp 127.0.0.1:20956: connect: connection refused
Reproduction steps
Setup Nomad with Consul integration and run the job file below
Job file (if appropriate)
Log for 'connect-proxy-count-api task'
Consul Log
Nomad Config
Consul config
The text was updated successfully, but these errors were encountered: