# Stack Monitoring Access Denied

**URL:** https://discuss.elastic.co/t/stack-monitoring-access-denied/350313
**Category:** Kibana
**Created:** [January 3, 2024, 2:09pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313 "2024-01-03T14:09:47Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![sourcreamnormanbates](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@sourcreamnormanbates](https://discuss.elastic.co/u/sourcreamnormanbates)
#### Post date: [January 3, 2024, 2:09pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313/1 "2024-01-03T14:09:47Z")

</div>

When I try to view Stack Monitoring, I receive an error message.  
I get the same message with the default elastic admin user as well as my provisioned unique admin user account I use.  
I only have one cluster, so I'm not sure why I'm getting this.

Access Denied

You are not authorized to access Monitoring. To use Monitoring, you need the privileges granted by both the `kibana_admin` and `monitoring_user ` roles.

If you are attempting to access a dedicated monitoring cluster, this might be because you are logged in as a user that is not configured on the monitoring cluster.

Since Cross Cluster Search is enabled (`monitoring.ui.ccs.enabled` is set to `true`), make sure your cluster has the `remote_cluster_client` role on at least one node

---

<div class="post-metadata">

### Author: ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)
#### Post date: [January 3, 2024, 6:31pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313/2 "2024-01-03T18:31:22Z")

</div>

Hi, @sourcreamnormanbates! Thanks for reaching out.

I found a couple of similar forum posts that might be worth checking out:

- [Access denied while opening Stack-Monitoring on Kibana 7.8](https://discuss.elastic.co/t/access-denied-while-opening-stack-monitoring-on-kibana-7-8/239947)
- [Kibana upgrade to 8.x , can't enter monitoring - #4 by matschaffer](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/4)

---

<div class="post-metadata">

### Author: ![sourcreamnormanbates](https://avatars.discourse-cdn.com/v4/letter/s/f05b48/32.png) [@sourcreamnormanbates](https://discuss.elastic.co/u/sourcreamnormanbates)
#### Post date: [January 3, 2024, 9:21pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313/3 "2024-01-03T21:21:20Z")

</div>

Thanks for the suggestions. The solution that worked for me was to add this setting to the kibana.yml.

monitoring.ui.ccs.enabled: false

---

<div class="post-metadata">

### Author: ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)
#### Post date: [January 3, 2024, 9:32pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313/4 "2024-01-03T21:32:48Z")

</div>

Thanks! Glad you found a solution!

---

<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: [January 31, 2024, 9:33pm UTC](https://discuss.elastic.co/t/stack-monitoring-access-denied/350313/5 "2024-01-31T21:33:06Z")

</div>

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