Vault server UI does not work

[NLRemco]

Describe the bug
Whenever a Vault dev server instance is spawned, navigating to the UI does not work as the browser does not accept the presented scripts.
Navigating to the website will result in the following errors in the console:

127.0.0.1/:1 Refused to execute script from 'http://127.0.0.1:8200/ui/assets/vendor-955807f07aa62cf6b124690f61829edf.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
127.0.0.1/:1 Refused to execute script from 'http://127.0.0.1:8200/ui/assets/vault-7e24f70a497a2e410d2aaedf982e8c75.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.
127.0.0.1/:1 Refused to execute script from 'http://127.0.0.1:8200/ui/sw-registration-1b862bc1e33e4a8a41781d56c3469209.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

To Reproduce
Steps to reproduce the behavior:

1. Start a Vault server instance. vault server -dev -dev-root-token-id=root -dev-listen-address=0.0.0.0:8200 or vault server -config=config.hcl
2. Open your browser.
3. Navigate to http://127.0.0.1:8200/ui

Expected behavior
The Vault server returns JavaScript files with the correct Content/MIME Type. Now the browser can securely execute said files.

Environment:

• Vault Server Version (retrieve with vault status): v1.9.x (any version above 1.8.9)
• Vault CLI Version (retrieve with vault version): Vault v1.9.4 (fcbe948b2542a13ee8036ad07dd8ebf8554f56cb), Vault v1.9.0
• Server Operating System/Architecture: Windows 10.0.19044 Build 19044

Additional Context:
Does not seem to happen on Docker version. Tested on Linux (Ubuntu 20.04.4 and Manjaro), seems to work fine.

[Inveracity]

seems related #13357

[aphorise]

golang/go#32350

Given then above merger - this issue will likely resolve as and when Vault adopts go 1.9.x which may be likely by Vault 1.13.x in 2023 (current track for core: Bump Go version to 1.18.5 in Vault 1.12.0).

Hey @RemcoBuddelmeijer meanwhile you may wish to refer to #13357 for more details and potential work-around solutions.

[zofskeez]

Closing since a fix was added to Go 1.19 and the issue should be resolved in Vault version >= 1.11.7

[AtiwadkarAjinkya]

Hi,
I am facing this issue for below version
Vault v1.17.3