# Yet again a run with on prem package-registry issue

**URL:** <https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [June 17, 2021, 5:09pm UTC](https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294 "2021-06-17T17:09:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![DartShinigami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dartshinigami/32/90480_2.png) [@DartShinigami](https://discuss.elastic.co/u/DartShinigami)\
**Post date:** [June 17, 2021, 5:09pm UTC](https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294/1 "2021-06-17T17:09:06Z")

</div>

I tried the workaround but with no luck any inside that you could provide me. I'm using kibana and elastic on docker ubuntu 20.04 here is my docker compose file for kibana.

```auto
kib01:
    image: docker.elastic.co/kibana/kibana:${VERSION}
    container_name: kib01
    depends_on: {"es01": {"condition": "service_healthy"}}
    ports:
      - 5601:5601    
    environment:
      SERVERNAME: localhost
      ELASTICSEARCH_URL: https://es01:9200
      ELASTICSEARCH_HOSTS: https://es01:9200
      ELASTICSEARCH_USERNAME: kibana_system
      ELASTICSEARCH_PASSWORD: GSdJ674nFKMwlRuYDZYB
      ELASTICSEARCH_SSL_CERTIFICATEAUTHORITIES: $CERTS_DIR/ca/ca.crt
      SERVER_SSL_ENABLED: "true"
      SERVER_SSL_KEY: $CERTS_DIR/kib01/kib01.key
      SERVER_SSL_CERTIFICATE: $CERTS_DIR/kib01/kib01.crt
      XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY: "emagF7vyXDZ6LKsTYdvwWXjgx6sx2GfK"
      XPACK_FLEET_REGISTRYURL: "http://localhost:8080"      
    volumes: 
      - certs:$CERTS_DIR
    networks:
      - elastic     
volumes:
  data01:
    driver: local
  data02:
    driver: local
  data03:
    driver: local
  certs:
    driver: local

networks: 
  elastic:
    driver: bridge

```

---

<div class="post-metadata">

**Author:** ![tiagocosta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tiagocosta/32/40045_2.png) [@tiagocosta](https://discuss.elastic.co/u/tiagocosta)\
**Post date:** [June 28, 2021, 2:13pm UTC](https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294/2 "2021-06-28T14:13:27Z")

</div>

@DartShinigami could you please detail what were the problem you were facing?

Cheers

---

<div class="post-metadata">

**Author:** ![DartShinigami](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dartshinigami/32/90480_2.png) [@DartShinigami](https://discuss.elastic.co/u/DartShinigami)\
**Post date:** [June 28, 2021, 3:12pm UTC](https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294/3 "2021-06-28T15:12:07Z")

</div>

Sorry for late response; I fix it BTW!!!!!. The error was trying to run the service in the same virtual machine with the elastic and kibana, I created another virtual machine and pointed the XPACK\_FLEET\_REGISTRYURL: to that one and all went fine.

Best Regards

---

<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:** [July 26, 2021, 3:12pm UTC](https://discuss.elastic.co/t/yet-again-a-run-with-on-prem-package-registry-issue/276294/4 "2021-07-26T15:12:17Z")

</div>

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