### Author:  [@samba1](https://discuss.elastic.co/u/samba1)
#### Post date: [February 6, 2016, 4:24am UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/1 "2016-02-06T04:24:07Z")
I'm following along with this: [https://www.elastic.co/guide/en/logstash/current/advanced-pipeline.html](https://www.elastic.co/guide/en/logstash/current/advanced-pipeline.html)
And was on the second part.
I decided to not do twitter to avoid signing up for a dev key and giving them my phone, and instead am just doing the beats part.
First I tried without SSL, and was getting the error:
`Beats Input: Remote connection closed {:peer=>"127.0.0.1:58326", :exception=>#, :level=>:warn}`
Then I added SSL stuff, and now get
```
The error reported is:
No message available
```
For reference, my logstash config is:
```
input {
beats {
port => "5043"
}
}
output {
elasticsearch {
}
file {
path => "/tmp/logstash-out"
}
}
```
and my filebeat.yml is
```
filebeat:
prospectors:
-
paths:
- "/var/log/*.log"
fields:
type: syslog
output:
elasticsearch:
enabled: true
hosts: ["http://localhost:5043"]
```
I'm just trying to get something going to see it working.
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 6, 2016, 4:28am UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/2 "2016-02-06T04:28:45Z")
You have beats sending directly to ES, not to LS, and on a bad port.
Maybe you intended to use the Logstash output as mentioned [here](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-getting-started.html#config-filebeat-logstash).
---
### Author:  [@samba1](https://discuss.elastic.co/u/samba1)
#### Post date: [February 6, 2016, 3:31pm UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/4 "2016-02-06T15:31:49Z")
I thought was odd, but I was following the guide (which I mis-linked originally, it's [https://www.elastic.co/guide/en/logstash/current/advanced-pipeline.html](https://www.elastic.co/guide/en/logstash/current/advanced-pipeline.html))
I feel like I tried that, as well, but I will try again.
---
### Author:  [@samba1](https://discuss.elastic.co/u/samba1)
#### Post date: [February 7, 2016, 4:44pm UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/7 "2016-02-07T16:44:30Z")
Setting it to localhost:5044 gives a "connection refused", even though logstash is indeed running.
That's because logstash does indeed run on port 5043, so the "elasticsearch" in the thing I linked is right, just mislabeled, I think.
Is there accurate documentation on connecting filebeats and logstash anywhere?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 9, 2016, 1:18am UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/8 "2016-02-09T01:18:47Z")
What's your config look like now?
---
### Author:  [@samba1](https://discuss.elastic.co/u/samba1)
#### Post date: [February 9, 2016, 11:57pm UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/9 "2016-02-09T23:57:26Z")
I've tried reducing it to just this:
```auto
input {
beats {
port => "5043"
}
}
output {
elasticsearch {
}
file {
path => "/tmp/logstash-out"
}
}
```
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 10, 2016, 12:18am UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/10 "2016-02-10T00:18:22Z")
What about filebeat?
---
### Author:  [@samba1](https://discuss.elastic.co/u/samba1)
#### Post date: [February 10, 2016, 10:15pm UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/11 "2016-02-10T22:15:12Z")
I've tried a number of setups, here's one:
```auto
filebeat:
prospectors:
-
paths:
- "/var/log/foo.log"
input_type: log
output:
elasticsearch:
hosts: ["localhost:9200"]
logstash:
hosts: ["localhost:5043"]
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 5:12am UTC](https://discuss.elastic.co/t/unable-to-get-logstash-guide-example-working/41109/12 "2017-07-06T05:12:10Z")