Getsockopt: connection refused

233 views
Skip to first unread message

Justas

unread,
Jan 20, 2017, 10:23:21 AM1/20/17
to Vault
Hi,

I have server with config:

backend "file" {
  address
= "127.0.0.1:8555"
  path
= "vault"
}

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

sudo netstat -tulpn | grep 8222

Outputs:

tcp        0      0 127.0.0.1:8222          0.0.0.0:*               LISTEN      11732/vault


When I use
vault status
on the same machine I get correct response but when I execute command with public IP address, I get
Error checking seal status: Get http://public-server-ip:8222/v1/sys/seal-status: dial tcp public-server-ip:8222: getsockopt: connection refused

How to solve this problem?

Justas




William Bengtson

unread,
Jan 20, 2017, 10:53:53 AM1/20/17
to Vault
Your config file shouldn't have 'address' in the backend for file.

Try something like this:

backend "file" {
  path = "/path/to/directory"
}

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

also, make sure you have VAULT_ADDR set to your the correct address.


--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/68b2e2bd-3828-46ff-af80-799bb3fcbf68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages