Getting Session error on Kibana UI

Elastic Stack Elasticsearch
1

image
image1784×992 74.9 KB

As shown in the screenshot , I’m having this issue . I tried a fresh installation and again after running for few days , I got this error again. I did some research and found that the roles for the kibana_system user is removed automatically and can’t be assigned manually . I don’t know if this is the exact issue or something else .
Please help me to resolve this error.

2

Now I got to know that it’s working on some laptops but not working on the others. I tried clearing the cache , changing the browsers and restarting the services . But the issue is persist for all laptops except a few.

3

8.11 is very old. Is there a chance that you can upgrade to at least 8.19.14 or better 9.3.3 version?

4

I upgraded it to latest version but still same issue . Actually I used this version because it is very stable and can be easily integrated with Wazuh.

5

Is your network behind proxy or secure? Might be some CDN sites are blocked, which cause errors during loading/working Kibana.
Start DevToolbar in your browser,vtrack what is happening with Kibana. Also make sure there is no errors in kibana.log

6

image
image1913×1002 102 KB

No errors in kibana.log and no proxy is being used . And this is the error in Network Tab.
But why is it working on some systems and not on others.

7

Hello @Cache_Digitech

If the URL is accessible from some laptop & not accessible from others , this means the issue is not with Kibana (ELK) but from the host/laptop where the URL is not accessible.

Few options is to try accessing the URL in incognito mode, if issue still persists it needs to be reviewed any common ground with the users who are facing this issue & the users who are able to access it without any problem.

Thanks!!

8

Already tried everything but the issue is still persist. In some laptops it's treating this capabilities request not as api call because of no cookies. But don't know why , cookies issue before login

9

Why are you using HTTP, have you try to use only HTTPS?

Here is response from Google AI:

  1. Common Scenarios
  • 401 Unauthorized Errors: Users often see 401 Unauthorized in browser developer tools despite correct credentials. This happens because the security level mismatch causes the browser to withhold necessary referrer information for authentication callbacks.
  • Integration Failures: Applications like Wazuh or JWT-based authentication may hang on "Loading Elastic" or fail to connect if the referrer policy is too strict or causing data loss between origins.
  1. Troubleshooting & Fixes
  • Clear Browser Cache/Cookies: As a first step, delete all stored cookies for the Kibana domain in your browser and reload.
  • Uniform HTTPS: Ensure the entire communication chain (User -> Proxy -> Kibana -> Elasticsearch) uses HTTPS to avoid protocol downgrades.
  • Kibana Configuration: Check your kibana.yml for CSP (Content Security Policy) settings. If you must change the policy, use the Kibana Guide to verify your csp.strict or csp.rules settings.
  • Reverse Proxy Adjustment: If using Nginx or Istio, you may need to explicitly set the Referrer-Policy header to strict-origin-when-cross-origin or another appropriate value to ensure headers are preserved while maintaining security.