# FIlebeat httpjson support for proxy connection

**URL:** <https://discuss.elastic.co/t/filebeat-httpjson-support-for-proxy-connection/250731>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [October 1, 2020, 7:03pm UTC](https://discuss.elastic.co/t/filebeat-httpjson-support-for-proxy-connection/250731 "2020-10-01T19:03:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scott\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scott_harris/32/45812_2.png) [@Scott\_Harris](https://discuss.elastic.co/u/Scott_Harris)\
**Post date:** [October 1, 2020, 7:03pm UTC](https://discuss.elastic.co/t/filebeat-httpjson-support-for-proxy-connection/250731/1 "2020-10-01T19:03:25Z")

</div>

I am attempting to configure filebeat 7.9.2 (running from docker image) to use the httpjson input. It works fine with an internally available URL but times outs on an external URL. I have verified and tried multiple combinations of the environment variables https\_proxy and http\_proxy. Upper and lower case including using a value that should return an immediate unathenticated error code.

Anyone have experience with this? Is this a known issue?

---

<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:** [October 29, 2020, 9:03pm UTC](https://discuss.elastic.co/t/filebeat-httpjson-support-for-proxy-connection/250731/2 "2020-10-29T21:03:26Z")

</div>

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