Vault: Vault OSS UI 404 page not found

Created on 12 Apr 2018  路  6Comments  路  Source: hashicorp/vault

Environment:
I just upgraded my vault from 0.9.6 to 0.10.0 and Vault UI is not reachable

  • Vault Version: 0.10.0
  • Operating System/Architecture: Centos7, docker

Vault Config File:

        storage "consul" {
          address = "consul.addr:port"
          path    = "consul.path"
          token   = "consul.token"
        }
        listener "tcp" {
          address     = "0.0.0.0:8200"
          tls_disable = true
        }

Startup Log Output:

==> Vault server configuration:

             Api Address: http://vault.addr
                     Cgo: disabled
         Cluster Address: https://vault.cluster.addr
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", tls: "disabled")
               Log Level: info
                   Mlock: supported: true, enabled: true
                 Storage: consul (HA available)
                 Version: Vault v0.10.0
             Version Sha: 5dd7f25f5c4b541f2da62d70075b6f82771a650d

==> Vault server started! Log data will stream in below:

2018-04-12T21:09:16.801Z [WARN ] storage.consul: appending trailing forward slash to path

Expected Behavior:

UI should be accessible

Actual Behavior:

I got 404 page not found.

Steps to Reproduce:

I don't know, I just use my web browser to the vault URL, I got 404 there, if I try /ui, I get a 404 too.

Important Factoids:

I'm upgrading from 0.9.6 to 0.10.0. I might be missing something, the documentation speaks of nothing in particular to enable UI, I tried in -dev mode and it works on my laptop.

Thanks for your help

Most helpful comment

I ran into this myself, mostly because I read the hashicorp guide and it doesn't mention it.

All 6 comments

Did you enable the UI via the configuration file or environment variable (VAULT_UI)?

The UI is enabled by default in -dev mode, but otherwise you'd have to explicitly enable it.

It seems that I fell asleep while reading the doc......

I'll try that, sorry for the inconvenience.

And thx for your help

I ran into this myself, mostly because I read the hashicorp guide and it doesn't mention it.

I'm having a slightly different issue with the Vault OSS docker image. Running in dev mode for a POC, i expected to be able to access the ui via port 8200 but i'm getting a connection refused. I'm running the version 0.11.0-beta1 image which i believe has the UI built in to it

@robertraybarnes you need to bind the container port to the host port if you want to access it from your host. Try adding -p 8200:8200 to your docker run ... command.

@calvn That did the trick in my local environment - thanks. I'm hosting vault on AKS in azure so i need to map the ports on that too

Was this page helpful?
0 / 5 - 0 ratings

Related issues

tustvold picture tustvold  路  3Comments

Wonder007 picture Wonder007  路  3Comments

adamroddick picture adamroddick  路  3Comments

maxsivanov picture maxsivanov  路  3Comments

0x9090 picture 0x9090  路  3Comments