# TCP Plugin Input Permission Denied

**URL:** https://discuss.elastic.co/t/tcp-plugin-input-permission-denied/127722
**Category:** Logstash
**Created:** [April 12, 2018, 3:36am UTC](https://discuss.elastic.co/t/tcp-plugin-input-permission-denied/127722 "2018-04-12T03:36:25Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)
#### Post date: [April 17, 2018, 5:11pm UTC](https://discuss.elastic.co/t/tcp-plugin-input-permission-denied/127722/5 "2018-04-17T17:11:07Z")

</div>

I'm not sure where you got `patchelf` as a solution from my suggestions; it appears to be unrelated; I'll quote the post I previously linked to below:

> [@Issue in Logstash after Upgrade](https://discuss.elastic.co/t/issue-in-logstash-after-upgrade/123421/2):
>
> I found a relevant issue on github, with comments that should provide a path forward:
> 
> > Ports in range 1 to 1024 are privileged and only root user can listen on it.
> > 
> > Options:
> > 
> > - run logstash as root (not a good idea)
> > - use setcap to grant java permission to use privileged ports
> > - use iptables or a proxy to forward port 514 to an unprivileged port.
> > 
> > -- [logstash will not open a listening port. · Issue #1587 · elastic/logstash · GitHub](https://github.com/elastic/logstash/issues/1587#issuecomment-50939823)
> 
> This blog post is specifically about using setcap to set capabilities for Java (although it references Java 7, and Logstash currently requires Java 8, so you may need to adjust it slightly):
> 
> [https://blogs.oracle.com/sduloutr/binding-a-server-to-privileged-port-on-linux-wo-running-as-root](https://blogs.oracle.com/sduloutr/binding-a-server-to-privileged-port-on-linux-wo-running-as-root)

---

_[View the full topic](https://discuss.elastic.co/t/tcp-plugin-input-permission-denied/127722)._