Kibana behind firewall

I have my kibana running behind firewall and can't connect to outside world. I don't need to connect either. it is working fine but

getting following error. how do I stop kibana to even trying.?

I already has this in kibana.yml

telemetry.optIn: false
xpack.fleet.enabled: false

[2024-03-28T16:24:44.631-05:00][ERROR][plugins.observabilityAIAssistant] Failed to resolve ELSER model definition: Error: Platinum, Enterprise or trial license needed
[2024-03-28T16:24:46.387-05:00][ERROR][plugins.fleet] Package needs to be manually reinstalled synthetics after installing Fleet global assets: Cannot reinstall an uploaded package
[2024-03-28T16:25:04.577-05:00][ERROR][plugins.securitySolution.telemetry_events] [task security:telemetry-configuration:1.0.0]: error scheduling task, received Request timed out
[2024-03-28T16:25:04.621-05:00][ERROR][plugins.apm] Failed to add API keys to APM package policies
[2024-03-28T16:25:04.624-05:00][ERROR][plugins.apm] TimeoutError: Request timed out
    at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:527:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at processTimers (node:internal/timers:511:9)
[2024-03-28T16:25:04.632-05:00][ERROR][plugins.apm] Failed to schedule APM source map migration
[2024-03-28T16:25:04.633-05:00][ERROR][plugins.apm] TimeoutError: Request timed out
    at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:527:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at listOnTimeout (node:internal/timers:540:9)
    at processTimers (node:internal/timers:514:7)
[2024-03-28T16:25:20.448-05:00][ERROR][plugins.fleet] Failed to fetch latest version of synthetics from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=synthetics&prerelease=false&kibana.version=8.13.0 failed, reason: read ECONNRESET
[2024-03-28T16:25:28.687-05:00][ERROR][plugins.fleet] Failed to fetch latest version of synthetics from registry: Error connecting to package registry: request to https://epr.elastic.co/search?package=synthetics&prerelease=true&kibana.version=8.13.0 failed, reason: read ECONNRESET
[2024-03-28T23:00:37.543-05:00][ERROR][plugins.taskManager] Task apm-telemetry-task "apm-telemetry-task" failed: ReferenceError: Cannot access 'collectAndStore' before initialization

1 Like

Salutations @elasticforme ,

To get started what version of our software are you running?

Also, which license do you have?

basic version 8.13.0

Ok I'm waiting to hear back from the team on what changes need to be made.
Thanks for asking!

Not sure about the other errors, but those seems to be related to the integrations as they are trying to connect to epr.elastic.co, which is the endpoint for the integrations packages.

Since a lot of things in Kibana now relies in integrations, I would expect some of them to not work right or throw some errors in the logs if it cannot access the epr endoint.

In this case you would need to have an air-gapped EPR as explained in this documentation.

@elasticforme

Can you try these settings please:

newsfeed.enabled: false
telemetry.optIn: false
map.includeElasticMapsService: false
1 Like

Great,
only one error message left and startup time of kibana reduce by lot

[2024-04-05T09:43:47.956-05:00][ERROR][plugins.observabilityAIAssistant] Failed to resolve ELSER model definition: Error: Platinum, Enterprise or trial license needed

Awesome!

Checking my colleagues now

Hello again.

If you're amenable to upgrading to 8.14, can you try this please: xpack.observabilityAIAssistant.enabled: false

man 8.14 is already out. this thing moves soooo fast I can't keep up. LOL

1 Like

8.14 is not out yet, the most recent is 8.13.2 which was released on Monday to fix an issue with the bundled java.

now all this changes made following unavailable

enterprise search
observability
secutiry

not that it matter to me at this time.

So, how are we doing here @elasticforme ?

Sounds like your deployment is not doing great?

no all good. I use what you suggested and kibana start time reduce by lot and also no more warning messages.

I did upgrade to 8.13.2 as well.