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

Starting server gives "Error initializing core: missing advertisement address" message #107

Closed
abaird opened this Issue Apr 30, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@abaird

abaird commented Apr 30, 2015

I was going through the docs today, particularly http://vaultproject.io/intro/getting-started/deploy.html where it gives a sample server config file and then has you run the following
vault server --config=example.hcl
However, when I use the configuration file, I get the following error:
Error initializing core: missing advertisement address
Here is the example.hcl file:

backend "consul" {
  address = "demo.consul.io:80"
  path = "abvault12345"
}

listener "tcp" {
 address = "127.0.0.1:8200"
 tls_disable = 1
}

It seems that when you use Consul backend, it needs the .hcl file to be more like this:

backend "consul" {
  address = "demo.consul.io:80"
  path = "abvault12345"
  advertise_addr = "127.0.0.1"
}

listener "tcp" {
 address = "127.0.0.1:8200"
 tls_disable = 1
}

(I have no idea what kind of address advertise_addr wants)

Using this file, I was able to get the server started successfully. You can read more about the server configuration here: http://vaultproject.io/docs/config/index.html#advertise_addr.

Also, in your examples, frequently the "--" is rendered as a long dash instead of two. Probably most people know about this, but it will trip up new users.

@sethvargo

This comment has been minimized.

Show comment
Hide comment
@sethvargo

sethvargo Apr 30, 2015

Contributor

Related to #103

Contributor

sethvargo commented Apr 30, 2015

Related to #103

@sethvargo sethvargo added bug labels Apr 30, 2015

@mitchellh

This comment has been minimized.

Show comment
Hide comment
@mitchellh

mitchellh May 2, 2015

Member

I'm going to just close as dup for #103, the solution will be the same.

Member

mitchellh commented May 2, 2015

I'm going to just close as dup for #103, the solution will be the same.

@mitchellh mitchellh closed this May 2, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment