Exactly what filebeat setup command did you run?
I asked this because a lot of folks just run setup with the –-dashboards and don't realize other assets need to be loaded. In fact, the most important ones need to be loaded,
You should just run
filebeat setup -e
My suggestion is to always get filebeat directly to Elasticsearch up and running and working first... And ONLY after this works ...then introduce Logstash.
So in short
Make this architecture work first
Filebeat -> Elasticsearch
Then get this architecture to work
Filebeat -> Logstash -> Elasticsearch
Here are the steps I would follow this example happens to be metricbeat but the same pattern applies for filebeat.