# Does kibana understand package registry via proxy?

**URL:** <https://discuss.elastic.co/t/does-kibana-understand-package-registry-via-proxy/281086>\
**Category:** Kibana\
**Created:** [August 11, 2021, 2:25pm UTC](https://discuss.elastic.co/t/does-kibana-understand-package-registry-via-proxy/281086 "2021-08-11T14:25:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\
**Post date:** [August 11, 2021, 2:25pm UTC](https://discuss.elastic.co/t/does-kibana-understand-package-registry-via-proxy/281086/1 "2021-08-11T14:25:21Z")

</div>

Hi,

Appearantly since 7.14 (fleet = GA) I am required to have internet access for my selfmanaged kibana's to reach some packet registry (or host one myself).

However, I set a proxy in the environment and am still not able to reach it. What is going wrong?  
The error:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/6/165360f1cc3c9f4e59a6ed95386bf96ab64ec2d7.png)

However from the commandline as the kibana user:

```auto
[kibana@aapps1121 ~]$ curl "https://epr.elastic.co/search?package=system&internal=true&experimental=true&kibana.version=7.14.0"
[
  {
    "name": "system",
    "title": "System",
    "version": "1.1.2",
    "release": "ga",
    "description": "This Elastic integration collects logs and metrics from your servers",
    "type": "integration",
    "download": "/epr/system/system-1.1.2.zip",
    "path": "/package/system/1.1.2",
    "icons": [
      {
        "src": "/img/system.svg",
        "path": "/package/system/1.1.2/img/system.svg",
        "title": "system",
        "size": "1000x1000",
        "type": "image/svg+xml"
      }
    ],
    "policy_templates": [
      {
        "name": "system",
        "title": "System logs and metrics",
        "description": "Collect logs and metrics from System instances"
      }
    ]
  }
][kibana@aapps1121 ~]$

```

I am running as kibana user:

```auto
[kibana@aapps1121 ~]$ ps -ef|grep kibana
kibana 62605 1 0 16:13 ? 00:00:00 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli/dist --logging.dest="/var/log/kibana/kibana.log" --pid.file="/run/kibana/kibana.pid"
kibana 62617 62605 4 16:13 ? 00:00:37 /usr/share/kibana/node/bin/node --preserve-symlinks-main --preserve-symlinks /usr/share/kibana/src/cli/dist --logging.dest="/var/log/kibana/kibana.log" --pid.file="/run/kibana/kibana.pid"

```

---

<div class="post-metadata">

**Author:** ![Tuckson](https://avatars.discourse-cdn.com/v4/letter/t/f14d63/32.png) [@Tuckson](https://discuss.elastic.co/u/Tuckson)\
**Post date:** [August 12, 2021, 1:04pm UTC](https://discuss.elastic.co/t/does-kibana-understand-package-registry-via-proxy/281086/2 "2021-08-12T13:04:01Z")

</div>

Solved by adding  
xpack.fleet.registryProxyUrl: "[http://proxy-url:8080](http://proxy-url:8080)" to kibana.yml

I find it bad practice that kibana does not make use of regular environment variables.

---

<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, 1:04pm UTC](https://discuss.elastic.co/t/does-kibana-understand-package-registry-via-proxy/281086/3 "2021-09-09T13:04:51Z")

</div>

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