# When ilm is enabled metricbeat can't communicate with kibana
**URL:** https://discuss.elastic.co/t/when-ilm-is-enabled-metricbeat-cant-communicate-with-kibana/302024
**Category:** Beats
**Tags:** beats-module, metricbeat
**Created:** [April 9, 2022, 12:14pm UTC](https://discuss.elastic.co/t/when-ilm-is-enabled-metricbeat-cant-communicate-with-kibana/302024 "2022-04-09T12:14:24Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Siavash\_Fazli](https://discuss.elastic.co/u/Siavash_Fazli)
#### Post date: [April 9, 2022, 12:14pm UTC](https://discuss.elastic.co/t/when-ilm-is-enabled-metricbeat-cant-communicate-with-kibana/302024/1 "2022-04-09T12:14:24Z")
Hi guys!!
I use ELK v7.16.2
I test the metricbeat on my test server with a direct connection (IP).
Now in the production environment, I use reverse proxy on ELK domains.
On the test environment, everything is ok, also I set my modified ilm policy, and works fine.
Now on the product environment, I got some errors:
```auto
2022-04-04T17:05:09.786+0430 ERROR [index-management.ilm] ilm/std.go:133 Index Alias metricbeat-7.16.2 setup failed: failed to create alias: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}: 405 Method Not Allowed: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}.
2022-04-04T17:05:09.786+0430 ERROR instance/beat.go:1015 Exiting: failed to create alias: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}: 405 Method Not Allowed: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}
Exiting: failed to create alias: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}: 405 Method Not Allowed: {"error":"Incorrect HTTP method for uri [/%3Cmetricbeat-7.16.2-%7Bnow/d%7D-000001%3E] and method [PUT], allowed: [POST]","status":405}
```
When I disable ilm setting in the metricbeat.yml file :
```auto
setup.ilm.enabled: false
```
now it works
```auto
root@data-sience:/home/dataroot# metricbeat setup -e
ILM policy and write alias loading not enabled.
Index setup finished.
Loading dashboards (Kibana must be running and reachable)
Loaded dashboards
```
On the other hand, indexes are being larger and larger, I have 8 servers, each index of them almost 1GB in 4 days.
Is the reverse proxy can cause this error (405)
How can I solve this?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 7, 2022, 2:14pm UTC](https://discuss.elastic.co/t/when-ilm-is-enabled-metricbeat-cant-communicate-with-kibana/302024/2 "2022-05-07T14:14:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.