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
Connect must be enabled in order to use this endpoint #6890
Comments
@celesteking The error message is referring to this setting which needs to be enabled on servers: https://www.consul.io/docs/agent/options.html#connect_enabled for Consul Connect (our service mesh feature) to work. Can I ask which tutorial you were following? I think the issue might be that the "getting started" guide is purposefully simplified and so uses an agent in If you can tell us a bit more about your process - which guides did you follow, what did you try next, we can maybe debug and make sure that path is clearer for others in the future. More details about Connect feature can be found here: https://www.consul.io/docs/connect/configuration.html |
Oh there is also this guide: https://learn.hashicorp.com/consul/developer-mesh/connect-production which walks through the steps/prerequisites that get you from a kick-the-tyres demo mode to a real production setup. |
I have followed the dev tutorial, now I'm onto prod tutorial. https://learn.hashicorp.com/consul/getting-started/join I'm able to reproduce the issue by starting up client with the following leftover config from dev tutorial:
After I remove the service with What is Connect and what is a mesh? The only thing that's used above is sidecar proxy feature. Just don't tell me you're using 3 different terms to describe 1 thing. We don't need sidecar proxy feature, it's irrelevant for our setup. |
Another thing I've noticed is that when you're doing things that supposed to fail, they don't fail, like deregistering a nonexistent service or You should do what redis does -- return an error (0) or ENOENT, but don't return SUCCESS. |
Also, the timing is wrong in all these docs pages. I can't be THAT stupid, but it takes me 10 minutes only to read the text and understand the pics on https://learn.hashicorp.com/consul/getting-started/services , not mentioning the time needed to actually mess around the commands and their output. Take an average Polish or whatever Finland person you might find nearby, make sure he knows no redis or whatever, and ask him to follow the tutorial. Measure how long it really takes. Another thing, the text Anyway, just my thoughts and I've only started... |
I'm still getting original error even after following docs:
servers were fed:
Still, no dice. Also, it seems like there's no way to view live server config, there's no such option. I'm not talking about |
Hi there! Sorry, but there is a second evening with consul here ) |
If you are running server agents in non For example:
Above command would start a consul server agent in a Docker container by joining in to an existing cluster by specifying IP (172.17.0.7) of a node in that cluster. The contents of All server agents can be restarted likewise one by one. Any server that boots up with this configuration and becomes a cluster leader will enable You can verify that
It should return CA config JSON. |
After upgrade to v1.11.3, I hit this problem too, the list of hosts for a service in Consul UI is not shown correctly. |
Getting this continuously on client after following the tutorial and trying to switch into production mode:
This endlessly appearing entirely cryptic message doesn't help at all. I'm trying start fresh with client config, it's been connected to servers and servers are in sync. I've deleted
/consul/data
to get rid of stale crap.consul leave
on client should really delete all stale data, if any was left from previous operation. This is client, not server, it should self-destruct and let me start anew.Client info
Server info
The text was updated successfully, but these errors were encountered: