# How to ship/fetch data from Client server which is not directly accessible to Logstash

**URL:** <https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130>\
**Category:** Logstash\
**Created:** [June 28, 2016, 8:46am UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130 "2016-06-28T08:46:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shubham\_deodia](https://avatars.discourse-cdn.com/v4/letter/s/a8b319/32.png) [@shubham\_deodia](https://discuss.elastic.co/u/shubham_deodia)\
**Post date:** [June 28, 2016, 8:46am UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130/1 "2016-06-28T08:46:51Z")

</div>

I had implemented ELK stack on my Localhost.

I want to Ship Data from Client server to ELK server.

I am able to do so , if client server is directly accessible from ELK server.

But, in production environment , the Client server is never directly accessible. Instead, we have to Hop (Proxy) between one or two server to access the Client server. (Redis might be able to help here, but i don't know how to implement it.

Also, I want to connect logstash to JDBC server which is present on Client server.

How can i fetch/Ship data from Client server in such case where Client server is not directly accessible.

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 30, 2016, 6:34pm UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130/2 "2016-06-30T18:34:59Z")

</div>

What kind of protocols do the proxies speak, i.e. what kind of traffic is allowed?

---

<div class="post-metadata">

**Author:** ![shubham\_deodia](https://avatars.discourse-cdn.com/v4/letter/s/a8b319/32.png) [@shubham\_deodia](https://discuss.elastic.co/u/shubham_deodia)\
**Post date:** [July 1, 2016, 5:32am UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130/3 "2016-07-01T05:32:14Z")

</div>

Only TCP

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [July 1, 2016, 5:37am UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130/4 "2016-07-01T05:37:48Z")

</div>

And they're SOCKS5 proxies or what? So you'd essentially need some piece of software on the client side that can speak SOCKS5 in order to call out to the Logstash process on the outside?

---

<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 6, 2017, 4:49am UTC](https://discuss.elastic.co/t/how-to-ship-fetch-data-from-client-server-which-is-not-directly-accessible-to-logstash/54130/5 "2017-07-06T04:49:58Z")

</div>

Closed on July 6, 2017, 4:49am UTC


