# Kibana cannot reach epr.elastic.co even though "chainpem" is set **URL:** https://discuss.elastic.co/t/kibana-cannot-reach-epr-elastic-co-even-though-chainpem-is-set/380858 **Category:** Kibana **Created:** [August 7, 2025, 8:58am UTC](https://discuss.elastic.co/t/kibana-cannot-reach-epr-elastic-co-even-though-chainpem-is-set/380858 "2025-08-07T08:58:37Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb) #### Post date: [August 8, 2025, 1:38pm UTC](https://discuss.elastic.co/t/kibana-cannot-reach-epr-elastic-co-even-though-chainpem-is-set/380858/5 "2025-08-08T13:38:46Z")
Are those logs from Kibana? > **[Set the proxy URL of the Elastic Package Registry | Elastic Docs](https://www.elastic.co/docs/reference/fleet/epr-proxy-setting)** > > Fleet might be unable to access the Elastic Package Registry because Kibana is behind a proxy server. Also your organization might have network traffic... Did you register the proxy? BTW minor, Kibana is nodejs not Java Also Others did get this to work with `NODE_EXTRA_CA_CERTS` > [@Kibana Fleet shows Self Signed Certificate in Certificate Chain](https://discuss.elastic.co/t/kibana-fleet-shows-self-signed-certificate-in-certificate-chain/297947/2): > > I was able to resolve this by suppling the root ca that my company uses and configuring the NODE\_EXTRA\_CA\_CERTS environment variable. For example: docker run --name kibana \ --net elastic \ -v $(pwd)/npmcerts.pem:/tmp/npmcerts.pem \ -e NODE\_EXTRA\_CA\_CERTS=/tmp/npmcerts.pem \ -p 5601:5601 \ docker.elastic.co/kibana/kibana:8.0.0 Did you try running like this. And made sure that file is readable by Kibana user / permissions are correct `NODE_EXTRA_CA_CERTS="/etc/kibana/CA_Bundle_2024.pem" /usr/share/kibana/bin/kibana` --- _[View the full topic](https://discuss.elastic.co/t/kibana-cannot-reach-epr-elastic-co-even-though-chainpem-is-set/380858)._