# Unable to initialize Ingest Manager behind proxy **URL:** \ **Category:** Kibana\ **Created:** [August 25, 2020, 9:08am UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255 "2020-08-25T09:08:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![iorfix](https://avatars.discourse-cdn.com/v4/letter/i/9fc348/32.png) [@iorfix](https://discuss.elastic.co/u/iorfix)\ **Post date:** [August 25, 2020, 9:08am UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/1 "2020-08-25T09:08:18Z")
Hi, I tried to use new beta Ingest Manager functionality. However, I got this error in Kibana when launching it: ```auto Unable to initialize Ingest Manager Error connecting to package registry at https://epr-7-9.elastic.co/search?package=endpoint&internal=true&experimental=true&kibana.version=7.9.0: request to https://epr-7-9.elastic.co/search?package=endpoint&internal=true&experimental=true&kibana.version=7.9.0 failed, reason: getaddrinfo ENOTFOUND epr-7-9.elastic.co epr-7-9.elastic.co:443 ``` The VM is behind a Proxy, and using a command line it is possible to fetch data, using curl: `curl -O "https://epr-7-9.elastic.co/search?package=system&internal=true&experimental=true&kibana.version=7.9.0"` I noticed there isn't any documented way to specify a connection proxy in Kibana. Any way to solve it? Thank you, Dario ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [August 25, 2020, 12:57pm UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/2 "2020-08-25T12:57:31Z")
Hi @iorfix Unfortunately, our current beta does not support a proxy. We have an option issue here discussion proxy support, best chime in here: [https://github.com/elastic/kibana/issues/70710](https://github.com/elastic/kibana/issues/70710) ---
**Author:** ![markn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/markn/32/74417_2.png) [@markn](https://discuss.elastic.co/u/markn)\ **Post date:** [September 11, 2020, 8:04am UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/3 "2020-09-11T08:04:05Z")
+1 if this is solved. We have multiple customers and also hosting a multi tenant platform. All behind proxies 🙂 ---
**Author:** ![aewing](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aewing/32/76392_2.png) [@aewing](https://discuss.elastic.co/u/aewing)\ **Post date:** [September 29, 2020, 5:27pm UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/4 "2020-09-29T17:27:34Z")
I'm a Heroku customer and I think I'm seeing this error after upgrading my Elastic resource. APM is failing with an error suggesting I have no ingest nodes (though my primary node is configured for ingest), and the Ingest Management screen in Kibana is displaying the error described above. ---
**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\ **Post date:** [September 30, 2020, 7:11am UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/5 "2020-09-30T07:11:13Z")
@aewing I think the two errors are not related. Could you create a separate topic for the "no ingest node" part? For your Heroku setup, I'm curious if you have put a proxy in front or if this just comes by default? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 28, 2020, 7:11am UTC](https://discuss.elastic.co/t/unable-to-initialize-ingest-manager-behind-proxy/246255/6 "2020-10-28T07:11:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.