# Error when running Filebeat to send log to Elasticsearch behind a reverse proxy
**URL:** https://discuss.elastic.co/t/error-when-running-filebeat-to-send-log-to-elasticsearch-behind-a-reverse-proxy/234017
**Category:** Beats
**Tags:** filebeat
**Created:** [May 23, 2020, 8:27pm UTC](https://discuss.elastic.co/t/error-when-running-filebeat-to-send-log-to-elasticsearch-behind-a-reverse-proxy/234017 "2020-05-23T20:27:00Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@aparasxidis](https://discuss.elastic.co/u/aparasxidis)
#### Post date: [May 23, 2020, 8:27pm UTC](https://discuss.elastic.co/t/error-when-running-filebeat-to-send-log-to-elasticsearch-behind-a-reverse-proxy/234017/1 "2020-05-23T20:27:00Z")
Hi, I'm running filebeat in docker, when I check the container logs I get:
`pipeline/output.go:105 Connection to backoff(elasticsearch(http://xxxxx.xxxxx.com:80/elastic)) established`
`Failed to perform any bulk index operations: 405 Method Not Allowed: {"error":"Incorrect HTTP method for uri [/] and method [POST], allowed: [GET, HEAD, DELETE]","status":405}`
Clearly, the connection is established, but I think this is related to the Nginx conf that I have for Elasticsearch because all the request are redirected to the root [/], if I change the endpoint for my host it ignores it and send me to the root, where you have the message with the cluster info.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 20, 2020, 8:27pm UTC](https://discuss.elastic.co/t/error-when-running-filebeat-to-send-log-to-elasticsearch-behind-a-reverse-proxy/234017/2 "2020-06-20T20:27:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.