# Kibana 403 response for super user elastic **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-security\ **Created:** [September 18, 2020, 6:23pm UTC](https://discuss.elastic.co/t/kibana-403-response-for-super-user-elastic/249154 "2020-09-18T18:23:27Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Seenivasan\_Gopalsamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seenivasan_gopalsamy/32/75830_2.png) [@Seenivasan\_Gopalsamy](https://discuss.elastic.co/u/Seenivasan_Gopalsamy)\ **Post date:** [September 18, 2020, 6:23pm UTC](https://discuss.elastic.co/t/kibana-403-response-for-super-user-elastic/249154/1 "2020-09-18T18:23:27Z")
Hello Team We are getting a 403 response after adding the index patterns. We are trying to move existing licenses to new servers due to disk space issue. Elastic, kibana, x-pack 6.2.2 403 Response Less Info OK Error: 403 Response [https://test-server/bundles/commons.bundle.js?v=16588:21:80798](https://test-server/bundles/commons.bundle.js?v=16588:21:80798) processQueue@[https://test-server/bundles/vendors.bundle.js?v=16588:116:132458](https://test-server/bundles/vendors.bundle.js?v=16588:116:132458) [https://test-server/bundles/vendors.bundle.js?v=16588:116:133361](https://test-server/bundles/vendors.bundle.js?v=16588:116:133361) $digest@[https://test-server/bundles/vendors.bundle.js?v=16588:116:144241](https://test-server/bundles/vendors.bundle.js?v=16588:116:144241) $apply@[https://test-server/bundles/vendors.bundle.js?v=16588:116:147025](https://test-server/bundles/vendors.bundle.js?v=16588:116:147025) done@[https://test-server/bundles/vendors.bundle.js?v=16588:116:100032](https://test-server/bundles/vendors.bundle.js?v=16588:116:100032) completeRequest@[https://test-server/bundles/vendors.bundle.js?v=16588:116:104705](https://test-server/bundles/vendors.bundle.js?v=16588:116:104705) [https://test-server/bundles/vendors.bundle.js?v=16588:116:105450](https://test-server/bundles/vendors.bundle.js?v=16588:116:105450) ---
**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\ **Post date:** [September 23, 2020, 1:49pm UTC](https://discuss.elastic.co/t/kibana-403-response-for-super-user-elastic/249154/2 "2020-09-23T13:49:15Z")
> [@Seenivasan\_Gopalsamy](#): > > We are getting a 403 response after adding the index patterns. Did you fix your disk space issue before creating the new index? That 403 is originated from Elasticsearch [Elasticsearch does not indicate retryability when flood stage is exceeded · Issue #49393 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/49393) This issue also provides some hints [Kibana stays read only when ES high disk watermark has been exceeded and later gone beneath the limit · Issue #13685 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/13685) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 21, 2020, 1:49pm UTC](https://discuss.elastic.co/t/kibana-403-response-for-super-user-elastic/249154/3 "2020-10-21T13:49:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.