# No access to Kibana WebUI via Nginx Proxy

**URL:** <https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989>\
**Category:** Kibana\
**Created:** [November 4, 2024, 8:39am UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989 "2024-11-04T08:39:54Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![sharbich](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sharbich](https://discuss.elastic.co/u/sharbich)\
**Post date:** [November 4, 2024, 10:31pm UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/21 "2024-11-04T22:31:18Z")

</div>

Hello Stephan,  
i don't see the value of my token. Is it possible that I'm not authorized?

```auto
root@dsme01:~# curl -X GET -u elastic "https://elasticsearch.intern.harnet.de:9200/_security/service/elastic/kibana/credential?pretty"
Enter host password for user 'elastic':
{
  "service_account" : "elastic/kibana",
  "count" : 1,
  "tokens" : {
    "token_tdmQ-JIBkQRpmbBNyIA8" : { }
  },
  "nodes_credentials" : {
    "_nodes" : {
      "total" : 1,
      "successful" : 1,
      "failed" : 0
    },
    "file_tokens" : { }
  }
}
root@dsme01:~# curl -X GET -u elastic "https://elasticsearch.intern.harnet.de:9200/_security/service/elastic/kibana/credential/token?pretty"
Enter host password for user 'elastic':
{
  "error" : "Incorrect HTTP method for uri [/_security/service/elastic/kibana/credential/token?pretty] and method [GET], allowed: [POST]",
  "status" : 405
}

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 4, 2024, 10:35pm UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/22 "2024-11-04T22:35:59Z")

</div>

> [@sharbich](#):
>
> `curl -X GET -`

If you want to **DELETE** you need to use `DELETE` and the token id

see [Here](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-delete-service-token.html)

```auto
DELETE /_security/service/<namespace>/<service>/credential/token/<token_name>

```

This is normal REST stuff, you need to looks at the API docs, use the Correct API, REST VERB etc...

So your command would be

```auto
curl -X DELETE -u elastic "https://elasticsearch.intern.harnet.de:9200/_security/service/elastic/kibana/credential/token/token_tdmQ-JIBkQRpmbBNyIA8"

```

---

<div class="post-metadata">

**Author:** ![sharbich](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sharbich](https://discuss.elastic.co/u/sharbich)\
**Post date:** [November 4, 2024, 10:46pm UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/23 "2024-11-04T22:46:47Z")

</div>

> [@stephenb](#):
>
> ```auto
> # "name": "token_3kPV-JIBSlnz2Y8IGKKq",
> # "value": "AAEAAWVsYXN0aWMva2liYW5hL3Rva2
> 
> ```

Why don't I see my token value?  
I understand the deleting.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 5, 2024, 12:09am UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/24 "2024-11-05T00:09:00Z")

</div>

When you create a token ...  
**like any other secret you only see it Once when it is created**... just like any other secret you are expected to copy it etc... you will never see the value again from the API, standard security practice

---

<div class="post-metadata">

**Author:** ![sharbich](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sharbich](https://discuss.elastic.co/u/sharbich)\
**Post date:** [November 5, 2024, 7:20am UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/25 "2024-11-05T07:20:11Z")

</div>

> [@stephenb](#):
>
> ```auto
> POST /_security/service/elastic/kibana/credential/token
> #{
> # "created": true,
> # "token": {
> # "name": "token_3kPV-JIBSlnz2Y8IGKKq",
> # "value": "AAEAAWVsYXN0aWMva2liYW5hL3Rva2VuX3drUFQtSklCU2xuejJZOElhNXdqOlJXc0RCMlJUUUNhel9aR1JubGlCWEE"
> # }
> #}
> 
> ```

Why do I see the token at the top of your configuration?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 5, 2024, 2:28pm UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/26 "2024-11-05T14:28:52Z")

</div>

Because that's the call when I created the service token the one time it was shown.  
The lines with  
`#` are the response /.results of the , `POST` not part request.

I was just trying to show you the flow.

If you create a token you will get a response. It will show the value once just when you created.

[Previous page](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989.md?page=1)
