Did you try to restart Kibana?
Also You should open a support ticket.
Yes, but somehow the supporter is not able to help me.
Already upgraded to 4 GB RAM from 1 GB RAM. No change.
Also restarted Kibana. I think some index is broken from seeing the logs. But nothing I can do. Also tried to restore from a previous snapshot. But cant get away the internal error...
Did you add setting to your kibana.yml?
When does that error occur?
When you try to log in?
When you try anonymous access?
It looks like you may have tried to enable anonymous access ...
Did you add setting to your kibana.yml?
- no
When does that error occur? - any time I try to access Kibana
When you try to log in? - always via Browser?
When you try anonymous access? - it does not matter, any access fails
It looks like you may have tried to enable anonymous access ... - yes before I did changes to my indices everything worked also the anon access...
I am confused did you or did you not enable anonymous access?
I would try to clear all settings that you have put in your elasticsearch.yml and your kibana.yml.
And what do you mean support could not help you?
Indeed anon access was enabled.
No changes on elasticsearch.yml were done.
Removed now any custom changes on kibana.yml.
Well until now support only said upgrade the RAM, but that didn't help anything...
Now after you removed settings have you restarted Kibana?
Have you tried in a different browser or incognito window?
If those don't work I would set elasticsearch back to 4GB and reopen new ticket on Kibana issue.
Yes. Latest Chrome and Firefox Incognito. Same error:
login_form_LoginForm/<@https://xxx.kb.northeurope.azure.elastic-cloud.com:9243/40865/bundles/plugin/security/8.0.0/security.chunk.4.js:8:22270
The Kibana ticket exists since 5 days already:
Your ticket is waiting on you.
You need to put in the error that you have there.
I would also open DevTools in Chrome and see if there's any errors there.
The steps you take to reproduce it in other words is that just when Kibana comes up or after you press the login button.
Include them all and be very specific about the error that you're having now.
1 Like
Ok we solved it. There were somehow freezed indicies.
Unfreezed them with POST insert_my_index/_unfreeze and now working properly again.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.