# Failed to decrypt report job data. Please re-generate this report. Kibana 6.7.1 **URL:** \ **Category:** Kibana\ **Created:** [September 23, 2019, 11:11am UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679 "2019-09-23T11:11:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![masterThomas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/masterthomas/32/42765_2.png) [@masterThomas](https://discuss.elastic.co/u/masterThomas)\ **Post date:** [September 23, 2019, 11:11am UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/1 "2019-09-23T11:11:04Z")
Hi team, i get error while generate PDF report. However, all server settings listed are made correctly. Use one instance of kibana. ``` Couldn't create report for dashboard 'New Dashboard'. Failed to decrypt report job data. Please re-generate this report. ``` ---
**Author:** ![masterThomas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/masterthomas/32/42765_2.png) [@masterThomas](https://discuss.elastic.co/u/masterThomas)\ **Post date:** [September 24, 2019, 10:55am UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/2 "2019-09-24T10:55:42Z")
team, any updates? ---
**Author:** ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)\ **Post date:** [September 26, 2019, 1:28pm UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/3 "2019-09-26T13:28:47Z")
Hi @masterThomas, Is there any server logs that get logged while generating your PDF report? If so, can you provide what you can? Thanks, Mike. ---
**Author:** ![masterThomas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/masterthomas/32/42765_2.png) [@masterThomas](https://discuss.elastic.co/u/masterThomas)\ **Post date:** [October 1, 2019, 12:52pm UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/4 "2019-10-01T12:52:37Z")
Hi @ [mikecote](https://discuss.elastic.co/u/mikecote), there is no any information in elastic and kibana logs about the PDF report generating . what should i look into? ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [October 1, 2019, 5:37pm UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/5 "2019-10-01T17:37:59Z")
Dear @masterThomas, There are a few things that this could be caused by. The main root cause is that Reporting is not able to decrypt information it found about a reporting job, because that data was encrypted under a different key. The quick fix is to make sure there is a `xpack.reporting.encryptionKey` in the kibana.yml file, and that key is the same for every instance of Kibana that uses the `.reporting-*` index pattern. 1. If there is not a `xpack.reporting.encryptionKey` setting in the kibana.yml file, Reporting will be forced to generate a new key for each server startup, and it will encrypt its jobs in `.reporting-*` using that encryption key. The problem that causes: jobs that were in pending status right before the server restarted are lost forever. The key that encrypted them was random and is no longer in the server's memory. 2. If there are multiple Kibana instances using the same Elasticsearch cluster, by default they will also use the same `.reporting-*` index pattern for Reporting storage. When that is done intentionally, it works very well because the instances can share the load of generating reports. It can unintentionally create a problem where one instance discovers a job that it shouldn't be able to. For the 6.7 version, the documentation has the details about how to handle either situation: - [https://www.elastic.co/guide/en/kibana/6.7/\_encryption\_keys\_for\_multiple\_kibana\_instances.html](https://www.elastic.co/guide/en/kibana/6.7/_encryption_keys_for_multiple_kibana_instances.html) - [https://www.elastic.co/guide/en/kibana/6.7/\_reporting\_indices\_for\_multiple\_kibana\_workspaces.html](https://www.elastic.co/guide/en/kibana/6.7/_reporting_indices_for_multiple_kibana_workspaces.html) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 29, 2019, 5:38pm UTC](https://discuss.elastic.co/t/failed-to-decrypt-report-job-data-please-re-generate-this-report-kibana-6-7-1/200679/6 "2019-10-29T17:38:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.