We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The vault login page UI appears broken and squashed when using Safari (looks fine on Chrome for example), happens every time
To Reproduce Steps to reproduce the behavior:
Expected behavior Expect the UI to appear properly and consistently across browsers.
Environment:
vault status
vault version
Vault server configuration file(s):
ui = true listener "tcp" { tls_disable = 0 address = "[::]:8200" cluster_address = "[::]:8201" tls_cert_file = "/vault/vault-ha-tls/vault.crt" tls_key_file = "/vault/vault-ha-tls/vault.key" tls_client_ca_file = "/vault/vault-ha-tls/vault.ca" telemetry { unauthenticated_metrics_access = "true" } } storage "raft" { path = "/vault/data" } disable_mlock = true service_registration "kubernetes" {} telemetry { prometheus_retention_time = "30s" disable_hostname = true }
Additional context Was not happening on previous versions of Vault, not sure which one this started on though
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The vault login page UI appears broken and squashed when using Safari (looks fine on Chrome for example), happens every time
To Reproduce
Steps to reproduce the behavior:
Can also scroll up a bit and see the vault logo is on the middle
And as I mentioned, all good on Chrome
Expected behavior
Expect the UI to appear properly and consistently across browsers.
Environment:
vault status
): 1.14.0vault version
): 1.15.6Vault server configuration file(s):
Additional context
Was not happening on previous versions of Vault, not sure which one this started on though
The text was updated successfully, but these errors were encountered: