# Kibana upgrade to 8.x , can't enter monitoring
**URL:** https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987
**Category:** Kibana
**Tags:** elastic-stack-monitoring
**Created:** [March 17, 2022, 8:06pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987 "2022-03-17T20:06:05Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@yhache](https://discuss.elastic.co/u/yhache)
#### Post date: [March 17, 2022, 8:06pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/1 "2022-03-17T20:06:05Z")
Hi, i did the upgrade of Elasticsearch and Kibana to the latest version and ever since, i am not able to get into the Stack Monitoring webpage ::
Here's the kibana.yml ::
```auto
server.host: "0.0.0.0"
server.publicBaseUrl: "https://cnq-elk.int.xxxxxxxxx.ca/"
server.name: "cnq-elk"
elasticsearch.hosts: ["https://127.0.0.1:9200"]
elasticsearch.username: "kibana_system"
elasticsearch.password: "xxxxxxxxxxxxxxxxxxxxxxx"
server.ssl.enabled: true
server.ssl.certificate: /etc/kibana/certs/kibana.pem
server.ssl.key: /etc/kibana/certs/kibana.key
elasticsearch.ssl.certificateAuthorities: ["/etc/kibana/certs/selfca.pem"]
```
And here my master node Elasticsearch.yml ::
```auto
cluster.name: cnq-elk
node.name: elk-node-1
node.roles: [master,data]
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: "0.0.0.0"
discovery.seed_hosts: ["127.0.0.1", "10.54.1.73"]
cluster.initial_master_nodes: ["elk-node-1"]
xpack.security.enabled: true
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.http.ssl.truststore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: certs/elastic-certificates.p12
cluster.max_shards_per_node: 10000
```
And finally, my data node Elasticsearch.yml ::
```auto
cluster.name: cnq-elk
node.name: elk-node-2
node.roles: [data,remote_cluster_client,ingest]
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: ["0.0.0.0"]
discovery.seed_hosts: ["127.0.0.1", "10.54.1.72"]
cluster.initial_master_nodes: ["elk-node-1"]
xpack.security.enabled: false
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.http.ssl.truststore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: certs/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: certs/elastic-certificates.p12
```
---
### Author:  [@matschaffer](https://discuss.elastic.co/u/matschaffer)
#### Post date: [April 4, 2022, 6:49am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/2 "2022-04-04T06:49:31Z")
Hi @yhache !
You'll need to add the `kibana_admin` and `monitoring_user` roles to the user you've used to authenticate with kibana.
[Configure security in Kibana | Kibana Guide [8.1] | Elastic](https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html) has some information on how to update the roles for elastic stack users.
---
### Author:  [@yhache](https://discuss.elastic.co/u/yhache)
#### Post date: [April 4, 2022, 11:55am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/3 "2022-04-04T11:55:19Z")
Thanks for the reply. I already gave all the access i could to the user. I even tried logging in with the "elastic" user. Nothing seems to be working.
---
### Author:  [@matschaffer](https://discuss.elastic.co/u/matschaffer)
#### Post date: [April 4, 2022, 11:56pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/4 "2022-04-04T23:56:40Z")
That's strange. The Elastic user should definitely work.
That message comes from [kibana/index.tsx at 9d662b77bec867247421376ecb60a07202ed45f9 · elastic/kibana · GitHub](https://github.com/elastic/kibana/blob/9d662b77bec867247421376ecb60a07202ed45f9/x-pack/plugins/monitoring/public/application/pages/access_denied/index.tsx#L51) which is a page I find hard to reach even in local testing.
It calls `api/monitoring/v1/check_access` ([kibana/check\_access.ts at 0bd772432a313599656d8fe8adfdc7e6ef5d328a · elastic/kibana · GitHub](https://github.com/elastic/kibana/blob/0bd772432a313599656d8fe8adfdc7e6ef5d328a/x-pack/plugins/monitoring/server/routes/api/v1/check_access/check_access.ts#L21)) on kibana so it could be that API is failing for some other reason and the UI is treating it as an authorization error.
If an exception gets thrown there it should show up in your kibana logs when you try to load the monitoring UI, so I'd recommend checking there next.
---
### Author:  [@matschaffer](https://discuss.elastic.co/u/matschaffer)
#### Post date: [April 5, 2022, 6:13am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/5 "2022-04-05T06:13:40Z")
Hi again @yhache !
I just came across [Stack Monitoring "access denied" after 8.0.0 upgrade · Issue #125756 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/125756) which seems to be caused by newer versions of Elasticsearch requiring `remote_cluster_client` for CCS to work, which stack monitoring queries by default.
You may be able to work around the problem by either configuring that role for your Elasticsearch nodes or setting `monitoring.ui.ccs.enabled: false` in kibana if you don't need the Stack Monitoring UI to query via CCS.
---
### Author:  [@yhache](https://discuss.elastic.co/u/yhache)
#### Post date: [April 5, 2022, 6:00pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/6 "2022-04-05T18:00:44Z")
> [@matschaffer](#):
>
> monitoring.ui.ccs.enabled: false
I only had my data instance with the role `remote_cluster_client` . So i added it to the master node and did a service reset.
Everything is working now. Thanks @matschaffer
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 3, 2022, 6:01pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-8-x-cant-enter-monitoring/299987/7 "2022-05-03T18:01:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.