# Kibana spaces fail to get status for filebeat agent while setup

**URL:** <https://discuss.elastic.co/t/kibana-spaces-fail-to-get-status-for-filebeat-agent-while-setup/289452>\
**Category:** Kibana\
**Created:** [November 17, 2021, 12:50pm UTC](https://discuss.elastic.co/t/kibana-spaces-fail-to-get-status-for-filebeat-agent-while-setup/289452 "2021-11-17T12:50:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rahul\_Kalshetty](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rahul_kalshetty/32/79589_2.png) [@Rahul\_Kalshetty](https://discuss.elastic.co/u/Rahul_Kalshetty)\
**Post date:** [November 17, 2021, 12:50pm UTC](https://discuss.elastic.co/t/kibana-spaces-fail-to-get-status-for-filebeat-agent-while-setup/289452/1 "2021-11-17T12:50:52Z")

</div>

Im using filebeat to push my logs to Elasticsearch directly. I have configured a kibana space in filebeat.yml but it is giving me error saying

```auto
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to https://kibana-host:9243/s/SPACE/api/status fails: Not Found: <nil>. Response: {"statusCode":404,"error":"Not Found","message":"Not Found"}.

```

My filebeat configuration looks like this:

```auto
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "https://kibana-host:9243"

  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  space.id: "SPACE"

```

Credentials are provided in elastic output.

---

<div class="post-metadata">

**Author:** ![brianseeders](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brianseeders/32/84831_2.png) [@brianseeders](https://discuss.elastic.co/u/brianseeders)\
**Post date:** [November 22, 2021, 8:21pm UTC](https://discuss.elastic.co/t/kibana-spaces-fail-to-get-status-for-filebeat-agent-while-setup/289452/2 "2021-11-22T20:21:17Z")

</div>

Hey @Rahul_Kalshetty,

Are you sure that the `SPACE` id you're using matches up with the `Identifier` field in `Management` -\> `Kibana` -\> `Spaces`? If it doesn't match, you would get this error.

I believe you would get an HTTP 401 instead of 404 if the user doesn't have access to that space, but it may also be worth making sure that the user filebeat is using has access.

Thanks  
Brian

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 20, 2021, 8:21pm UTC](https://discuss.elastic.co/t/kibana-spaces-fail-to-get-status-for-filebeat-agent-while-setup/289452/3 "2021-12-20T20:21:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.