# How to disable attempts to connect to the package registry?

**URL:** <https://discuss.elastic.co/t/how-to-disable-attempts-to-connect-to-the-package-registry/280516>\
**Category:** Kibana\
**Created:** [August 5, 2021, 9:38am UTC](https://discuss.elastic.co/t/how-to-disable-attempts-to-connect-to-the-package-registry/280516 "2021-08-05T09:38:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fadenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadenb/32/92572_2.png) [@fadenb](https://discuss.elastic.co/u/fadenb)\
**Post date:** [August 5, 2021, 9:38am UTC](https://discuss.elastic.co/t/how-to-disable-attempts-to-connect-to-the-package-registry/280516/1 "2021-08-05T09:38:15Z")

</div>

Hi,

We are operating an Elastic stack in an environment that is **intentionally** unable to access the outside world/internet.  
When we browse to our Kibana dashboards, we see that our browsers are trying to fetch `/api/fleet/epm/packages?experimental=true`, which times out after a while with errors like this:

```auto
"Error connecting to package registry: request to https://epr.elastic.co/search?experimental=true&kibana.version=7.13.1 failed, reason: connect ENETUNREACH 34.120.127.130:443"

```

It seems that every time the browser calls the `/api/fleet/epm/packages?experimental=true` endpoint the server tries to fetch something from `epr.elastic.co` which will never work in our environment.

Is there any way to disable those checks?  
It is visually annoying and will (by design) never succeed 🙂

Thanks!

---

<div class="post-metadata">

**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:** [August 12, 2021, 6:07pm UTC](https://discuss.elastic.co/t/how-to-disable-attempts-to-connect-to-the-package-registry/280516/2 "2021-08-12T18:07:04Z")

</div>

Hi, it sounds like you are not using the fleet plugin (Ingest Manager) in your environment. Why not just turn off the plugin in kibana.yml?

```auto
xpack.fleet.enabled: false

```

If you are using Ingest Manager, you can track this issue to find when a self-managed package registry will be supported: [Provide self-managed package-registry that backs integrations UI · Issue #1178 · elastic/integrations · GitHub](https://github.com/elastic/integrations/issues/1178)

---

<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:** [September 9, 2021, 6:08pm UTC](https://discuss.elastic.co/t/how-to-disable-attempts-to-connect-to-the-package-registry/280516/3 "2021-09-09T18:08:03Z")

</div>

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