I am trying to run hashicorp vault server as windows service in windows 10 system. Vault server UI is showing as blank screen. Please refer my configuration details.
config.hcl
ui = true
backend "consul" {
address = "127.0.0.1:8500"
path = "vault/"
}
listener "tcp" {
address = "127.0.0.1:8200"
tls_disable = 1
tls_cert_file = "c:/vault/config/certificate.crt"
tls_key_file = "c:/vault/config/privkey.key"
}
By default vault server is running in this (http://localhost:8200/ui/) local URL. When i navigate to this 8200 port , Blank ui screen is displayed.
But at the same time hashicorp vault server UI is loading if we run vault as container based application.
Windows service command I used to run vault service:
sc.exe create VaultAgent binPath= "C:\vault\vault.exe server -config=C:\vault\config\config.hcl" displayName= "Vault Agent" start= auto
Note: vault.exe is downloaded from vault windows amd64 version this url.
I am able to receive the response from vault server. Please refer the image. vault server backend response
Note: Consul service is up and running. Please refer the image. consul server up and running
How to bring up the Vault server UI up and running? Am i missing something.?
Note: Below are the Vault server UI console logs
unseal:1 Refused to execute script from 'https://localhost:8200/ui/assets/vendor-dd308e6ebdb070a5a829a0c0d6e74f61.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
unseal:1 Refused to execute script from 'https://localhost:8200/ui/assets/vault-8a8f62829e5ad33487e21f63af47c80d.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
unseal:1 Refused to execute script from 'https://localhost:8200/ui/sw-registration-1b862bc1e33e4a8a41781d56c3469209.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
Latest version of the Hashicorp is having an bug and it is in opened stage. Please refer the url. GitHub issue link
So you can little go back with old version(1.8.8) of vault and try to run it as windows service and UI should be up and running.
Note: v 1.8.8 is having it's own feature and not having all the features of the latest vault version.