This is most often caused by a firewall or anti-virus. It could be on same machine running Filebeat, the network in between, or on the ES server.
You can test the HTTP HEAD request that Filebeat uses independent of Filebeat by running the command given here.