This issue occurred when we tried to implement https. We are rolling back after some problems but now http connection to the vault doesn't work. We looked online to find several solutions that doesn't quite apply to us. So we are having issues with a vault instance that was working but doesn't seem to be listening anymore.
The vault status responds with the following
Error checking seal status: Get http://127.0.0.1:8200/v1/sys/seal-status: dial tcp 127.0.0.1:8200: connect: connection refused
our config.hcl has this for the listener
After modifying the vault we make sure to stop and start the vault service.
env | grep VAULT returns the following value
VAULT_ADDR=http://127.0.0.1:8200
I looked around online and these two links seem to have similar issues
https://github.com/hashicorp/vault/issues/2944
https://groups.google.com/forum/#!topic/vault-tool/yL6QUC9snKI
The tips mentioned in the links above didn't seem to help. I'm wondering if this is an issue with changing a configuration file on a running vault.
Let me know if you need more information.
This email and any files transmitted with it are confidential.
Unauthorized publication, use or dissemination of this email is prohibited. --
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/8e987ae9-efdd-4474-a29d-c69eb2a6b03a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.