Kibana Reporting plugin not working

I have ELK - 7.10.0 - OSS version and standalone opendistro plugins. I have an issue with reporting plugin. Whenever, I try download report, it always gives error “Error Downloading Report”. Reports contains PNG of dashboard.

Also, I found following logs in elasticsearch log file.

[2021-01-13T13:50:56,282][INFO ][c.a.o.r.a.ReportInstanceActions] [data-1] reports:ReportInstance-info ubS1-3YB7ttttqXFrb1B
[2021-01-13T13:50:56,292][WARN ][c.a.o.r.a.PluginBaseAction] [data-1] reports:ElasticsearchStatusException: message:Permission denied for Report Definition ubS1-3YB7ttttqXFrb1B

How can I download reports ?

Similar issue here but another error. Just upgraded the whole stack (including beats) and started playing around with reports. Reports get generated (based on dashboard) but once I click on ‘PNG’ icon to down load, I get “Error downloading report” message. Kibana logs show a bizarre error indicating that it tries to connect to the localhost:5601 (why???) while my Kibana is not running on default URL at all. Obviously, I did not find anything about the respective configuration (I just hoped that maybe some specific definition for reporting is required in order to let the plugin know about Kibana’s URL).

{“type”:“log”,“@timestamp”:“2021-01-13T20:58:28Z”,“tags”:[“error”,“plugins”,“opendistroReportsKibana”],“pid”:29377,“message”:"Error: net::ERR_CONNECTION_REFUSED at http://localhost:5601/app/dashboards#/view/826ab760-ee8e-11ea-a949-4f7c89c35c0b?_g=(time:(from:‘2021-01-13T20:20:33.222Z’,to:‘2021-01-13T20:50:33.222Z’))\

@dhruvil7doshi and @igorid70 I would go ahead and an issue in at the github repo if you haven’t already GitHub - opendistro-for-elasticsearch/kibana-reports: Kibana Reports .

@searchymcsearchface - thanks, just found this:

I just wonder how it is possible to release a new feature which only works with default host and default port. Really don’t know whether to laugh or to cry

Is there any workaround that can be implemented until the next update ?

I manually builded Kibana source code and then kibana-reports on my local machine. After then, I installed the newly built Kibana Reports on another ELK-7.10-OSS version. But still I am not able to download PNG/PDF reports.

Here is the kibana.log when generating report

log [14:25:04.399] [error][opendistroReportsKibana][plugins] Failed to generate report by id: Error: Failed to launch chrome! spawn /usr/share/kibana/plugins/opendistroReportsKibana/server/routes/utils/…/…/…/.chromium/headless_shell ENOENT

TROUBLESHOOTING: puppeteer/ at main · puppeteer/puppeteer · GitHub

log [14:25:04.400] [error][opendistroReportsKibana][plugins] Error: Failed to launch chrome! spawn /usr/share/kibana/plugins/opendistroReportsKibana/server/routes/utils/…/…/…/.chromium/headless_shell ENOENT

TROUBLESHOOTING: puppeteer/ at main · puppeteer/puppeteer · GitHub

at onClose (/usr/share/kibana/plugins/opendistroReportsKibana/node_modules/puppeteer-core/lib/Launcher.js:348:14)
at ChildProcess.helper.addEventListener.error (/usr/share/kibana/plugins/opendistroReportsKibana/node_modules/puppeteer-core/lib/Launcher.js:339:64)
at ChildProcess.emit (events.js:198:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
at onErrorNT (internal/child_process.js:415:16)
at process._tickCallback (internal/process/next_tick.js:63:19)

error [14:25:04.319] Error: Internal Server Error
at HapiResponseAdapter.toError (/usr/share/kibana/src/core/server/http/router/response_adapter.js:132:19)
at HapiResponseAdapter.toHapiResponse (/usr/share/kibana/src/core/server/http/router/response_adapter.js:86:19)
at HapiResponseAdapter.handle (/usr/share/kibana/src/core/server/http/router/response_adapter.js:81:17)
at Router.handle (/usr/share/kibana/src/core/server/http/router/router.js:164:34)
at process._tickCallback (internal/process/next_tick.js:68:7)

I am new to linux environment. How do I use below URL for troubleshooting ?
puppeteer/ at main · puppeteer/puppeteer · GitHub

You can expect a fix of the related github issue above, in next ODFE release

Moved to reporting category.

If you build from source, the fail to launch Chrome error seems that you don’t have Chromium artifacts placed in the right place, which is ..../kibana-reports/.chromium. You need to create that directory if needed. The artifacts for each OS are available here.