$ vault statusThere was this issue suggesting it was a problem with the storage backend. In my case it was having HTTP_PROXY set in the environment and the proxy won't allow the connection. unset HTTP_PROXY fixed the issue.
Error checking seal status: Get https://vault.internal-domain:8200/v1/sys/seal-status: Forbidden
exactly my problem. Good catch!ReplyDelete