# \[SOLVED\] TCP "RST"/reset causing Filebeat/Logstash connection reset

**URL:** <https://discuss.elastic.co/t/solved-tcp-rst-reset-causing-filebeat-logstash-connection-reset/82343>\
**Category:** Logstash\
**Created:** [April 13, 2017, 6:50pm UTC](https://discuss.elastic.co/t/solved-tcp-rst-reset-causing-filebeat-logstash-connection-reset/82343 "2017-04-13T18:50:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![gtorrance](https://avatars.discourse-cdn.com/v4/letter/g/8edcca/32.png) [@gtorrance](https://discuss.elastic.co/u/gtorrance)\
**Post date:** [April 14, 2017, 11:42am UTC](https://discuss.elastic.co/t/solved-tcp-rst-reset-causing-filebeat-logstash-connection-reset/82343/3 "2017-04-14T11:42:59Z")

</div>

I'm embarrassed it took me so long to solve this.

Turns out all I needed to do was specify a client\_inactivity\_timeout of more than the default of 60 seconds. In my particular situation the client (on a test server) was relatively inactive, causing Logstash to kill the connection after 60 seconds. Increasing this beyond the inactivity time resolved the issue.

```
input {
  beats {
    client_inactivity_timeout => 1200
    port => 5044
  }
}

```

Thanks,  
Greg

---

_[View the full topic](https://discuss.elastic.co/t/solved-tcp-rst-reset-causing-filebeat-logstash-connection-reset/82343)._