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

Kibana throws an error after logging in at IE11 #50927

Closed
kertal opened this issue Nov 18, 2019 · 4 comments · Fixed by #52248
Closed

Kibana throws an error after logging in at IE11 #50927

kertal opened this issue Nov 18, 2019 · 4 comments · Fixed by #52248
Labels
bug Fixes for quality problems that affect the customer experience IE11 Team:Operations Team label for Operations Team

Comments

@kertal
Copy link
Member

kertal commented Nov 18, 2019

Kibana version:
master

Elasticsearch version:
master

Server OS version:

Browser version:
IE11
Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:

Steps to reproduce:

  1. try to login into Kibana on IE11
  2. You get the "Something went wrong" error

Expected behavior:

Screenshots (if relevant):
Bildschirmfoto 2019-11-18 um 16 27 37

@kertal kertal added bug Fixes for quality problems that affect the customer experience Team:Operations Team label for Operations Team IE11 labels Nov 18, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@patrykkopycinski
Copy link
Contributor

I did some investigation and I think 9769be3 caused that

@FrankHassanabad
Copy link
Contributor

@alexwizp, do you think the above error is coming from this PR as @patrykkopycinski is suggesting above?
#50182

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-arch (Team:AppArch)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience IE11 Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants