# Kibana - Method not Allowed **URL:** \ **Category:** Kibana\ **Created:** [February 21, 2020, 7:15pm UTC](https://discuss.elastic.co/t/kibana-method-not-allowed/220443 "2020-02-21T19:15:25Z")\ **Posts on this page:** 4\ **Page:** 1

**Author:** ![andreluizpr](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@andreluizpr](https://discuss.elastic.co/u/andreluizpr)\ **Post date:** [February 21, 2020, 7:15pm UTC](https://discuss.elastic.co/t/kibana-method-not-allowed/220443/1 "2020-02-21T19:15:26Z")

Hello everyone I'm starting now with ELK. I installed my environment on a lightsail server on AWS and it has the following configuration: CentOS 7.7.1908 Elasticsearch 7.6.0 - Release 1 Kibana 7.6.0 - Release 1 Logstash 7.6.0 Nginx 1.17.8 - reverse proxy I managed to make all the configuration of the environment without any difficulty. On the client machine, I configured the filebeat, auditbeat, metricbeat and packetbeat to communicate with Elastisearch on port 9200 and Kibana on port 5601. I did not use Logstash because I was in no way able to make his GeoIP filter work for Nginx logs. No filter just works. With direct sending to Elasticserch the information is displayed without a problem. This however is not the biggest problem I encountered (if anyone knows how to help me with this I appreciate it). The big problem is that every time I access a dashboard (filebeat / auditbeat / metricbeat / packetbeat) I get the following message: Error fetching fields for index pattern filebeat-7.6.0- \* (ID: aa189950-54a4-11ea-a7bd-0768c3c180e6) Method Not Allowed When I click to show details, I have this: \_construct @ https: [//logserver.domain.com/bundles/commons.bundle.js:](https://logserver.domain.com/bundles/commons.bundle.js:) 3: 2994490 Wrapper @ https: [//logserver.domain.com/bundles/commons.bundle.js:](https://logserver.domain.com/bundles/commons.bundle.js:) 3: 2993589 HttpFetchError @ https: [//logserver.domain.com/bundles/commons.bundle.js:](https://logserver.domain.com/bundles/commons.bundle.js:) 3: 2995366 fetchResponse $ @ https: [//logserver.domain.com/bundles/commons.bundle.js:](https://logserver.domain.com/bundles/commons.bundle.js:) 3: 2991052 s @ https: [//logserver.domain.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:](https://logserver.domain.com/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:) 338: 774546 l / i.\_invoke \ **Author:** ![andreluizpr](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@andreluizpr](https://discuss.elastic.co/u/andreluizpr)\ **Post date:** [February 21, 2020, 7:38pm UTC](https://discuss.elastic.co/t/kibana-method-not-allowed/220443/2 "2020-02-21T19:38:28Z") Hello guys, Sorry for my post above. Analyzing better after doing it, I saw that it was a problem related to NGINX, which erroneously had the configuration below: if ( request\_method! ~ ^ (GET | HEAD | POST) ) { return 405; } The CTRL C CTRL V of another configuration betrayed me. Thanks, Andre ---

**Author:** ![tiagocosta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tiagocosta/32/40045_2.png) [@tiagocosta](https://discuss.elastic.co/u/tiagocosta)\ **Post date:** [March 18, 2020, 6:18pm UTC](https://discuss.elastic.co/t/kibana-method-not-allowed/220443/3 "2020-03-18T18:18:19Z")

@andreluizpr I'll close the topic and mark your answer as the solution. Thanks for letting us know! ---