Skip to content
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

Unable to access UI or API via NodePort in dev mode #451

Closed
jamesmmchugh opened this issue Jan 21, 2021 · 4 comments
Closed

Unable to access UI or API via NodePort in dev mode #451

jamesmmchugh opened this issue Jan 21, 2021 · 4 comments

Comments

@jamesmmchugh
Copy link

I'm installing the chart with the following values:

server:
  dev:
    enabled: true
    # Set VAULT_DEV_ROOT_TOKEN_ID value
    devRootToken: "something"
  service:
    enabled: true
    type: "NodePort"
ui:
  enabled: true
  serviceType: "NodePort"

However I always get 'connection refused' when I try and connect to either the UI or the API.
i.e.

export VAULT_ADDR='http://{myNode}:{servceNodePort}'
vault status
Error checking seal status: Get "http://{myNode}:{servceNodePort}/v1/sys/seal-status": dial tcp {nodeIP}:{serviceNodePort}: connect: connection refused

Other services exposed as NodePorts and in the cluster all work as expected.

@tvoran
Copy link
Member

tvoran commented Jan 23, 2021

Hi @jamesmmchugh this is probably due to a bug that was fixed in #446. We'll probably be releasing it in the next couple weeks.

In the meantime, you can try setting VAULT_DEV_LISTEN_ADDRESS to "[::]:8200" to work around it.

server:
  extraEnvironmentVars:
    VAULT_DEV_LISTEN_ADDRESS: "[::]:8200"

@tuteng
Copy link

tuteng commented Jan 24, 2021

I have the same problem

@jamesmmchugh
Copy link
Author

Hi @jamesmmchugh this is probably due to a bug that was fixed in #446. We'll probably be releasing it in the next couple weeks.

In the meantime, you can try setting VAULT_DEV_LISTEN_ADDRESS to "[::]:8200" to work around it.

server:
  extraEnvironmentVars:
    VAULT_DEV_LISTEN_ADDRESS: "[::]:8200"

This worked for me in the meantime. Thanks.

@tvoran
Copy link
Member

tvoran commented Jan 27, 2021

@jamesmmchugh Glad to hear it worked! I'll go ahead and close this issue for now.

@tuteng If the workaround isn't helping your issue, I'd suggest asking a question in our discuss forum to hit a wider audience.

@tvoran tvoran closed this as completed Jan 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants