(/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/util/executeSchedule.js:8:9)
at AsyncAction._execute (/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:76:18)
at AsyncAction.execute (/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncAction.js:64:26)
at AsyncScheduler.flush (/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/scheduler/AsyncScheduler.js:39:33)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
[2023-04-16T07:34:27.837+00:00][ERROR][plugins.screenshotting.browser-driver] Error: Protocol error (Performance.getMetrics): Session closed. Most likely the page has been closed.
at CDPSessionImpl.send (/usr/share/kibana/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:316:35)
at Object.kill (/usr/share/kibana/x-pack/plugins/screenshotting/server/browsers/chromium/driver_factory/index.js:167:51)
at /usr/share/kibana/x-pack/plugins/screenshotting/server/browsers/chromium/driver_factory/index.js:204:24
at execFinalizer (/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/Subscription.js:172:9)
at OperatorSubscriber.Subscription.unsubscribe (/usr/share/kibana/node_modules/rxjs/dist/cjs/internal/Subscription.js:89:29)
...
```
## Environment
Elastic/Kibana version: `8.5.3`
OS: `CentOS Linux release 7.5.1804 (Core)`
Kibana is connected via a proxy (Nginx) over https, but I have configured reporting to use http with:
```auto
xpack.reporting.kibanaServer.port: 5601
xpack.reporting.kibanaServer.protocol: http
xpack.reporting.kibanaServer.hostname: monitor.mydomain.com
```
Have increased the timeout to `2m`:
```auto
xpack.screenshotting.capture.timeouts.openUrl: 2m
```
Other relevant configuration:
```auto
server.host: "0.0.0.0"
server.publicBaseUrl: "http://monitor.mydomain.com"
server.ssl.enabled: false
server.name: "monitor.mydomain.com"
```
The reverse proxy SSL cert is a self-signed cert.
Is this error an indication of misconfiguration of the `xpack.reporting.kibanaServer.*` properties?
The closest I have found on this specific error is [this SO post](https://stackoverflow.com/questions/68383589/error-protocol-error-fetch-continuerequest-invalid-interceptionid), and poster had solved their own issue by fixing invalid resources (presumably invalid URLs). So I suspect it is something to do with the reverse proxy configuration.
Regards,
Simon
---
### Author:  [@sblack](https://discuss.elastic.co/u/sblack)
#### Post date: [April 23, 2023, 10:59pm UTC](https://discuss.elastic.co/t/reporting-diagnostics-tool-fails-on-capture-screenshot/330080/2 "2023-04-23T22:59:32Z")
Update:
I have tried the following with no further success:
- Disabled SE Linux.
- Enabled NGINX to support just `http`.
- Made sure the the executable `/usr/share/kibana/x-pack/plugins/screenshotting/chromium/headless_shell-linux_x64/headless_shell` is owned by `kibana`.
But I am now getting a different error in Kibana: `Gateway Time-out`
When running with puppeteer debugging, still seeing the `Protocol error (Fetch.continueRequest): Invalid InterceptionId.` error.
Appreciate any other suggestions.
Regards,
Simon
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 21, 2023, 11:00pm UTC](https://discuss.elastic.co/t/reporting-diagnostics-tool-fails-on-capture-screenshot/330080/3 "2023-05-21T23:00:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.