# 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:** 1
**Showing post:** 5
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [November 4, 2024, 4:38pm UTC](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989/5 "2024-11-04T16:38:56Z")
What version are you on? Ohh I see 8.15.3
Did you try to create a new service account token?
> **[Create service account token API | Elasticsearch Guide \[8.15\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/security-api-create-service-token.html)**
Perhaps look at this similar thread, did you create the token via CLI or API?
Perhaps recreate the service token with the API
> [@Kibana not starting after making service account changes for upgrade to 8](https://discuss.elastic.co/t/kibana-not-starting-after-making-service-account-changes-for-upgrade-to-8/297406/4):
>
> The CLI creates a service token in a file, which is not replicated. The API creates a service token in an index, which is replicated. The URL method and path are of the form: POST /\_security/service/\/\/credential/token/\ Perhaps one of these curl examples would work: $ curl -s -X POST -u elastic:PASSWORD "ADDRESS:9200/\_security/service/elastic/kibana/credential/token/token1" $ curl -s -X POST -H 'Authorization: Bearer TOKEN' "ADDRESS:9200/\_security/service/ela…
Also I would always get everything working before you put a proxy in front... eliminate the variables
---
_[View the full topic](https://discuss.elastic.co/t/no-access-to-kibana-webui-via-nginx-proxy/369989)._