# Reporting error Request-URI Too Long / Reporting error Bad Request

**URL:** <https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [December 9, 2018, 2:44pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050 "2018-12-09T14:44:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jerzy\_Stopa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerzy_stopa/32/31842_2.png) [@Jerzy\_Stopa](https://discuss.elastic.co/u/Jerzy_Stopa)\
**Post date:** [December 9, 2018, 2:44pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/1 "2018-12-09T14:44:12Z")

</div>

Hello,  
Elastic cloud 6.5.2 / Kibana 6.5.2 for some dashboards, when requesting PDF report I receive error:  
Reporting error Request-URI Too Long

I didn't experience this before upgrading to 6.5  
Dashboard is correctly rendered on screen.

When switching to external Kibana server (elastic search on elastic cloud, kibana 6.5.2 installed on EC2 from rpm) I got : Reporting error Bad Request

For other dashboards I get pdf without problems

---

<div class="post-metadata">

**Author:** ![bryan\_stuhlsatz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bryan_stuhlsatz/32/49123_2.png) [@bryan\_stuhlsatz](https://discuss.elastic.co/u/bryan_stuhlsatz)\
**Post date:** [December 9, 2018, 4:35pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/2 "2018-12-09T16:35:40Z")

</div>

I dont know if this will help or not. It definitely allows the IE browser lovers to use Kibana. IE does not support long URL's. Change the Kibana advanced setting of: state:storeInSessionStorage to "On"

---

<div class="post-metadata">

**Author:** ![Jerzy\_Stopa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerzy_stopa/32/31842_2.png) [@Jerzy\_Stopa](https://discuss.elastic.co/u/Jerzy_Stopa)\
**Post date:** [December 9, 2018, 9:04pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/3 "2018-12-09T21:04:00Z")

</div>

> [@bryan\_stuhlsatz](#):
>
> state:storeInSessionStorage

I tested it and it didn't help.  
I am using chrome normally but the problems seems to be not browser related

---

<div class="post-metadata">

**Author:** ![Jerzy\_Stopa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerzy_stopa/32/31842_2.png) [@Jerzy\_Stopa](https://discuss.elastic.co/u/Jerzy_Stopa)\
**Post date:** [December 12, 2018, 4:47pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/4 "2018-12-12T16:47:28Z")

</div>

Elastic team please give any guidance what to do?

---

<div class="post-metadata">

**Author:** ![Jerzy\_Stopa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerzy_stopa/32/31842_2.png) [@Jerzy\_Stopa](https://discuss.elastic.co/u/Jerzy_Stopa)\
**Post date:** [December 16, 2018, 8:40pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/5 "2018-12-16T20:40:46Z")

</div>

Problem continues with 6.5.3. Only small dashboards are processed. Bad request for bigger, that worked fine in 6.4.x

---

<div class="post-metadata">

**Author:** ![JohanRask](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johanrask/32/22713_2.png) [@JohanRask](https://discuss.elastic.co/u/JohanRask)\
**Post date:** [December 20, 2018, 8:54am UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/6 "2018-12-20T08:54:25Z")

</div>

Any news on this? We are seeing this in 6.5.1 and it is a blocker for us.

---

<div class="post-metadata">

**Author:** ![Jerzy\_Stopa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jerzy_stopa/32/31842_2.png) [@Jerzy\_Stopa](https://discuss.elastic.co/u/Jerzy_Stopa)\
**Post date:** [December 22, 2018, 12:11pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/7 "2018-12-22T12:11:58Z")

</div>

> [@Jerzy\_Stopa](#):
>
> Reporting error Request-URI Too Long

6.5.4 same problem  
I issued bug in github: Reporting error Request-URI Too Long #27728

> <https://github.com/elastic/kibana/issues/27728>
>
> \*\*Kibana version:\*\*
> 6.5.2 to 6.5.4
> 
> \*\*Elasticsearch version:\*\*
> 6.5.2 to 6.5.…4
> 
> \*\*Server OS version:\*\*
> Elastic cloud
> \*\*Browser version:\*\*
> 
> \*\*Browser OS version:\*\*
> 
> \*\*Original install method (e.g. download page, yum, from source, etc.):\*\*
> 
> \*\*Describe the bug:\*\*
> Generate pdf report in Kibana results in Reporting error Request-URI Too Long for medium size and big dashboars (message: Bad request for Kibana installed on own hosted server using yum)
> Small reports work correctly
> 
> \*\*Steps to reproduce:\*\*
> 1. Open dashboard with several visualisation in it (~10 is enough)
> 2. Choose shar/PDF report
> 3. Click generate report 
> 
> \*\*Expected behavior:\*\*
> report processing startes
> \*\*Screenshots (if relevant):\*\*
> 
> \*\*Errors in browser console (if relevant):\*\*
> 
> \*\*Provide logs and/or server output (if relevant):\*\*
> 
> \*\*Any additional context:\*\*
> please see https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 19, 2019, 12:11pm UTC](https://discuss.elastic.co/t/reporting-error-request-uri-too-long-reporting-error-bad-request/160050/8 "2019-01-19T12:11:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
