# Unable to access Elastic Search from Browser

**URL:** <https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241>\
**Category:** Search Guard\
**Created:** [December 10, 2018, 12:37pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241 "2018-12-10T12:37:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Venkata\_Naresh\_Divi](https://avatars.discourse-cdn.com/v4/letter/v/c5a1d2/32.png) [@Venkata\_Naresh\_Divi](https://forum.search-guard.com/u/Venkata_Naresh_Divi)\
**Post date:** [December 10, 2018, 12:37pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241/1 "2018-12-10T12:37:56Z")

</div>

When asking questions, please provide the following information:

- Search Guard and Elasticsearch version

6.4.3

- Installed and used enterprise modules, if any

- JVM version and operating system version

JAVA 10.0.2, Ubuntu 18.04

- Search Guard configuration files

basic\_internal\_auth\_domain:  
enabled: true  
order: 0  
http\_authenticator:  
type: basic  
challenge: false  
authentication\_backend:  
type: intern  
saml\_auth\_domain\_okta:  
http\_enabled: true  
transport\_enabled: true  
order: 1  
http\_authenticator:  
type: ‘saml’  
challenge: true  
config:  
idp:  
metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml  
entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )  
sp:  
entity\_id: kibana-saml-demo  
kibana\_url: [https://kibana.](https://kibana./)\*\*\*\*.info:5601/  
roles\_key: Role  
exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’  
authentication\_backend:  
type: noop

``

- Elasticsearch log messages on debug level

- Other installed Elasticsearch or Kibana plugins, if any

Elasticsearch.yml:

```auto
searchguard.enterprise_modules_enabled: true

searchguard.ssl.transport.pemcert_filepath: CN=emailnow.info.crtfull.pem
searchguard.ssl.transport.pemkey_filepath: CN=emailnow.info.key.pem
searchguard.ssl.transport.pemkey_password: $$$$$$$$$$$$$$$$$$
searchguard.ssl.transport.pemtrustedcas_filepath: chain-ca.pem
searchguard.ssl.transport.enforce_hostname_verification: false

searchguard.ssl.http.enabled: true
searchguard.compliance.history.internal_config_enabled: true
searchguard.compliance.history.external_config_enabled: true
searchguard.compliance.history.read.metadata_only: true

searchguard.ssl.http.pemcert_filepath: CN=emailnow.info.crtfull.pem
searchguard.ssl.http.pemkey_filepath: CN=emailnow.info.key.pem
searchguard.ssl.http.pemkey_password: $$$$$$$$$$$$$$$$$$$$$$
searchguard.ssl.http.pemtrustedcas_filepath: chain-ca.pem
searchguard.allow_unsafe_democertificates: true
searchguard.authcz.admin_dn:
  - CN=sgadmin

searchguard.audit.type: internal_elasticsearch
searchguard.enable_snapshot_restore_privilege: true
searchguard.check_snapshot_restore_write_privileges: true
searchguard.restapi.roles_enabled: ["sg_all_access"]
cluster.routing.allocation.disk.threshold_enabled: false
cluster.name: searchguard_demo
network.host: 0.0.0.0
discovery.zen.minimum_master_nodes: 1
node.max_local_storage_nodes: 3
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.ml.enabled: false
xpack.security.enabled: false
xpack.watcher.enabled: false

I have set the https for elastic search and Im able to access the elastic search from server and through curl. But Unable to access it from browser and getting the below exception.

```

{“error”:{“root\_cause”:[{“type”:“security\_exception”,“reason”:“no permissions for [cluster:monitor/main] and User [name=sg\_anonymous, roles=[sg\_anonymous\_backendrole], requestedTenant=null]”}],“type”:“security\_exception”,“reason”:“no permissions for [cluster:monitor/main] and User [name=sg\_anonymous, roles=[sg\_anonymous\_backendrole], requestedTenant=null]”},“status”:403}

```auto

```

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [December 10, 2018, 1:04pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241/2 "2018-12-10T13:04:16Z")

</div>

Can you please attach the complete sg\_config.yml (attached as file, not copy and paste)?

> **···**
>
> On Monday, 10 December 2018 13:37:56 UTC+1, Venkata Naresh Divi wrote:
> 
> > When asking questions, please provide the following information:
> 
> > - Search Guard and Elasticsearch version
> 
> > 6.4.3
> 
> > - Installed and used enterprise modules, if any
> 
> > - JVM version and operating system version
> 
> > JAVA 10.0.2, Ubuntu 18.04
> 
> > - Search Guard configuration files
> 
> > basic\_internal\_auth\_domain:  
> > enabled: true  
> > order: 0  
> > http\_authenticator:  
> > type: basic  
> > challenge: false  
> > authentication\_backend:  
> > type: intern  
> > saml\_auth\_domain\_okta:  
> > http\_enabled: true  
> > transport\_enabled: true  
> > order: 1  
> > http\_authenticator:  
> > type: ‘saml’  
> > challenge: true  
> > config:  
> > idp:  
> > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml  
> > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )  
> > sp:  
> > entity\_id: kibana-saml-demo  
> > kibana\_url: [https://kibana.](https://kibana./)\*\*\*\*.info:5601/  
> > roles\_key: Role  
> > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’  
> > authentication\_backend:  
> > type: noop
> 
> > ``
> 
> > 
> 
> > 
> 
> > - Elasticsearch log messages on debug level
> 
> > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > 
> 
> > Elasticsearch.yml:
> 
> > ```auto
> > searchguard.enterprise_modules_enabled: true
> > 
> > searchguard.ssl.transport.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > searchguard.ssl.transport.pemkey_filepath: CN=emailnow.info.key.pem
> > searchguard.ssl.transport.pemkey_password: $$$$$$$$$$$$$$$$$$
> > searchguard.ssl.transport.pemtrustedcas_filepath: chain-ca.pem
> > searchguard.ssl.transport.enforce_hostname_verification: false
> > 
> > searchguard.ssl.http.enabled: true
> > searchguard.compliance.history.internal_config_enabled: true
> > searchguard.compliance.history.external_config_enabled: true
> > searchguard.compliance.history.read.metadata_only: true
> > 
> > searchguard.ssl.http.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > searchguard.ssl.http.pemkey_filepath: CN=emailnow.info.key.pem
> > searchguard.ssl.http.pemkey_password: $$$$$$$$$$$$$$$$$$$$$$
> > searchguard.ssl.http.pemtrustedcas_filepath: chain-ca.pem
> > searchguard.allow_unsafe_democertificates: true
> > searchguard.authcz.admin_dn:
> > - CN=sgadmin
> > 
> > searchguard.audit.type: internal_elasticsearch
> > searchguard.enable_snapshot_restore_privilege: true
> > searchguard.check_snapshot_restore_write_privileges: true
> > searchguard.restapi.roles_enabled: ["sg_all_access"]
> > cluster.routing.allocation.disk.threshold_enabled: false
> > cluster.name: searchguard_demo
> > network.host: 0.0.0.0
> > discovery.zen.minimum_master_nodes: 1
> > node.max_local_storage_nodes: 3
> > xpack.monitoring.enabled: true
> > xpack.graph.enabled: false
> > xpack.ml.enabled: false
> > xpack.security.enabled: false
> > xpack.watcher.enabled: false
> > 
> > ```
> 
> > I have set the https for elastic search and Im able to access the elastic search from server and through curl. But Unable to access it from browser and getting the below exception.
> 
> > 
> 
> > ```auto
> > {"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"},"status":403}
> > 
> > ```

---

<div class="post-metadata">

**Author:** ![Venkata\_Naresh\_Divi](https://avatars.discourse-cdn.com/v4/letter/v/c5a1d2/32.png) [@Venkata\_Naresh\_Divi](https://forum.search-guard.com/u/Venkata_Naresh_Divi)\
**Post date:** [December 10, 2018, 1:11pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241/3 "2018-12-10T13:11:22Z")

</div>

> Can you please attach the complete sg\_config.yml (attached as file, not copy and paste)?
> 
> > When asking questions, please provide the following information:

> > - Search Guard and Elasticsearch version

> > 6.4.3

> > - Installed and used enterprise modules, if any

> > - JVM version and operating system version

> > JAVA 10.0.2, Ubuntu 18.04

> > - Search Guard configuration files

> > basic\_internal\_auth\_domain:  
> > enabled: true  
> > order: 0  
> > http\_authenticator:  
> > type: basic  
> > challenge: false  
> > authentication\_backend:  
> > type: intern  
> > saml\_auth\_domain\_okta:  
> > http\_enabled: true  
> > transport\_enabled: true  
> > order: 1  
> > http\_authenticator:  
> > type: ‘saml’  
> > challenge: true  
> > config:  
> > idp:  
> > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml  
> > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )  
> > sp:  
> > entity\_id: kibana-saml-demo  
> > kibana\_url: [https://kibana.](https://kibana./)\*\*\*\*.info:5601/  
> > roles\_key: Role  
> > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’  
> > authentication\_backend:  
> > type: noop

> > ``

> >

> >

> > - Elasticsearch log messages on debug level

> > - Other installed Elasticsearch or Kibana plugins, if any

> >

> > Elasticsearch.yml:

> > ```auto
> > searchguard.enterprise_modules_enabled: true
> > 
> > searchguard.ssl.transport.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > searchguard.ssl.transport.pemkey_filepath: CN=emailnow.info.key.pem
> > searchguard.ssl.transport.pemkey_password: $$$$$$$$$$$$$$$$$$
> > searchguard.ssl.transport.pemtrustedcas_filepath: chain-ca.pem
> > searchguard.ssl.transport.enforce_hostname_verification: false
> > 
> > searchguard.ssl.http.enabled: true
> > searchguard.compliance.history.internal_config_enabled: true
> > searchguard.compliance.history.external_config_enabled: true
> > searchguard.compliance.history.read.metadata_only: true
> > 
> > searchguard.ssl.http.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > searchguard.ssl.http.pemkey_filepath: CN=emailnow.info.key.pem
> > searchguard.ssl.http.pemkey_password: $$$$$$$$$$$$$$$$$$$$$$
> > searchguard.ssl.http.pemtrustedcas_filepath: chain-ca.pem
> > searchguard.allow_unsafe_democertificates: true
> > searchguard.authcz.admin_dn:
> > - CN=sgadmin
> > 
> > searchguard.audit.type: internal_elasticsearch
> > searchguard.enable_snapshot_restore_privilege: true
> > searchguard.check_snapshot_restore_write_privileges: true
> > searchguard.restapi.roles_enabled: ["sg_all_access"]
> > cluster.routing.allocation.disk.threshold_enabled: false
> > cluster.name: searchguard_demo
> > network.host: 0.0.0.0
> > discovery.zen.minimum_master_nodes: 1
> > node.max_local_storage_nodes: 3
> > xpack.monitoring.enabled: true
> > xpack.graph.enabled: false
> > xpack.ml.enabled: false
> > xpack.security.enabled: false
> > xpack.watcher.enabled: false
> > 
> > ```

> > I have set the https for elastic search and Im able to access the elastic search from server and through curl. But Unable to access it from browser and getting the below exception.

> >

> > ```auto
> > {"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"},"status":403}
> > 
> > ```

[sg\_config.yml](https://forum.search-guard.com/uploads/short-url/shpFxcVQdGvlrb2vfWJS4bYybIf.yml) (9.99 KB)

> **···**
>
> On Monday, 10 December 2018 18:34:16 UTC+5:30, Search Guard wrote:
> 
> > On Monday, 10 December 2018 13:37:56 UTC+1, Venkata Naresh Divi wrote:

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [December 10, 2018, 1:49pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241/4 "2018-12-10T13:49:09Z")

</div>

are you sure this is the config file which is loaded?

From the above mentioned error it looks like that there is anonymous authentication enabled.

After you make changes to sg\_config.yml you need to push them via sgadminto become effective.

Can you provide elasticsearch logs (on debug level if possible)?

> **···**
>
> On Monday, 10 December 2018 14:11:22 UTC+1, Venkata Naresh Divi wrote:
> 
> > On Monday, 10 December 2018 18:34:16 UTC+5:30, Search Guard wrote:
> > 
> > > Can you please attach the complete sg\_config.yml (attached as file, not copy and paste)?
> > > 
> > > On Monday, 10 December 2018 13:37:56 UTC+1, Venkata Naresh Divi wrote:
> > > 
> > > > When asking questions, please provide the following information:
> 
> > > > - Search Guard and Elasticsearch version
> 
> > > > 6.4.3
> 
> > > > - Installed and used enterprise modules, if any
> 
> > > > - JVM version and operating system version
> 
> > > > JAVA 10.0.2, Ubuntu 18.04
> 
> > > > - Search Guard configuration files
> 
> > > > basic\_internal\_auth\_domain:  
> > > > enabled: true  
> > > > order: 0  
> > > > http\_authenticator:  
> > > > type: basic  
> > > > challenge: false  
> > > > authentication\_backend:  
> > > > type: intern  
> > > > saml\_auth\_domain\_okta:  
> > > > http\_enabled: true  
> > > > transport\_enabled: true  
> > > > order: 1  
> > > > http\_authenticator:  
> > > > type: ‘saml’  
> > > > challenge: true  
> > > > config:  
> > > > idp:  
> > > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml  
> > > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )  
> > > > sp:  
> > > > entity\_id: kibana-saml-demo  
> > > > kibana\_url: [https://kibana.](https://kibana./)\*\*\*\*.info:5601/  
> > > > roles\_key: Role  
> > > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’  
> > > > authentication\_backend:  
> > > > type: noop
> 
> > > > ``
> 
> > > >
> 
> > > >
> 
> > > > - Elasticsearch log messages on debug level
> 
> > > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > > >
> 
> > > > Elasticsearch.yml:
> 
> > > > ```auto
> > > > searchguard.enterprise_modules_enabled: true
> > > > 
> > > > searchguard.ssl.transport.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > > > searchguard.ssl.transport.pemkey_filepath: CN=emailnow.info.key.pem
> > > > searchguard.ssl.transport.pemkey_password: $$$$$$$$$$$$$$$$$$
> > > > searchguard.ssl.transport.pemtrustedcas_filepath: chain-ca.pem
> > > > searchguard.ssl.transport.enforce_hostname_verification: false
> > > > 
> > > > searchguard.ssl.http.enabled: true
> > > > searchguard.compliance.history.internal_config_enabled: true
> > > > searchguard.compliance.history.external_config_enabled: true
> > > > searchguard.compliance.history.read.metadata_only: true
> > > > 
> > > > searchguard.ssl.http.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > > > searchguard.ssl.http.pemkey_filepath: CN=emailnow.info.key.pem
> > > > searchguard.ssl.http.pemkey_password: $$$$$$$$$$$$$$$$$$$$$$
> > > > searchguard.ssl.http.pemtrustedcas_filepath: chain-ca.pem
> > > > searchguard.allow_unsafe_democertificates: true
> > > > searchguard.authcz.admin_dn:
> > > > - CN=sgadmin
> > > > 
> > > > searchguard.audit.type: internal_elasticsearch
> > > > searchguard.enable_snapshot_restore_privilege: true
> > > > searchguard.check_snapshot_restore_write_privileges: true
> > > > searchguard.restapi.roles_enabled: ["sg_all_access"]
> > > > cluster.routing.allocation.disk.threshold_enabled: false
> > > > cluster.name: searchguard_demo
> > > > network.host: 0.0.0.0
> > > > discovery.zen.minimum_master_nodes: 1
> > > > node.max_local_storage_nodes: 3
> > > > xpack.monitoring.enabled: true
> > > > xpack.graph.enabled: false
> > > > xpack.ml.enabled: false
> > > > xpack.security.enabled: false
> > > > xpack.watcher.enabled: false
> > > > 
> > > > ```
> 
> > > > I have set the https for elastic search and Im able to access the elastic search from server and through curl. But Unable to access it from browser and getting the below exception.
> 
> > > >
> 
> > > > ```auto
> > > > {"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"},"status":403}
> > > > 
> > > > ```

---

<div class="post-metadata">

**Author:** ![searchguard\_google\_group](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.search-guard.com/searchguard_google_group/32/462_2.png) [@searchguard\_google\_group](https://forum.search-guard.com/u/searchguard_google_group)\
**Post date:** [December 10, 2018, 1:55pm UTC](https://forum.search-guard.com/t/unable-to-access-elastic-search-from-browser/1241/5 "2018-12-10T13:55:43Z")

</div>

pls provide also the kibana.yml and make sure you followed

[SAML Authentication | Security for Elasticsearch | Search Guard](https://docs.search-guard.com/latest/saml-authentication) and

> **[Using SAML with Kibana | Search Guard | Security for Elasticsearch](https://search-guard.com/kibana-elasticsearch-saml/)**
>
> Search Guard fully supports for SAML, so you can use your favorite identity provider like Keycloak, Okta or Auth0 to implement easy Kibana Single Sign-On.

> **···**
>
> On Monday, 10 December 2018 14:49:10 UTC+1, Search Guard wrote:
> 
> > are you sure this is the config file which is loaded?
> 
> > From the above mentioned error it looks like that there is anonymous authentication enabled.
> 
> > 
> 
> > After you make changes to sg\_config.yml you need to push them via sgadminto become effective.
> 
> > 
> 
> > Can you provide elasticsearch logs (on debug level if possible)?
> 
> > On Monday, 10 December 2018 14:11:22 UTC+1, Venkata Naresh Divi wrote:
> > 
> > > On Monday, 10 December 2018 18:34:16 UTC+5:30, Search Guard wrote:
> > > 
> > > > Can you please attach the complete sg\_config.yml (attached as file, not copy and paste)?
> > > > 
> > > > On Monday, 10 December 2018 13:37:56 UTC+1, Venkata Naresh Divi wrote:
> > > > 
> > > > > When asking questions, please provide the following information:
> 
> > > > > - Search Guard and Elasticsearch version
> 
> > > > > 6.4.3
> 
> > > > > - Installed and used enterprise modules, if any
> 
> > > > > - JVM version and operating system version
> 
> > > > > JAVA 10.0.2, Ubuntu 18.04
> 
> > > > > - Search Guard configuration files
> 
> > > > > basic\_internal\_auth\_domain:  
> > > > > enabled: true  
> > > > > order: 0  
> > > > > http\_authenticator:  
> > > > > type: basic  
> > > > > challenge: false  
> > > > > authentication\_backend:  
> > > > > type: intern  
> > > > > saml\_auth\_domain\_okta:  
> > > > > http\_enabled: true  
> > > > > transport\_enabled: true  
> > > > > order: 1  
> > > > > http\_authenticator:  
> > > > > type: ‘saml’  
> > > > > challenge: true  
> > > > > config:  
> > > > > idp:  
> > > > > metadata\_file: /home/ubuntu/ELK\_6\_4\_Stack/elasticsearch-6.4.3/config/okta.xml  
> > > > > entity\_id: [http://www.okta.com/\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*](http://www.okta.com/ *************** )  
> > > > > sp:  
> > > > > entity\_id: kibana-saml-demo  
> > > > > kibana\_url: [https://kibana.](https://kibana./)\*\*\*\*.info:5601/  
> > > > > roles\_key: Role  
> > > > > exchange\_key: ‘eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9’  
> > > > > authentication\_backend:  
> > > > > type: noop
> 
> > > > > ``
> 
> > > > >
> 
> > > > >
> 
> > > > > - Elasticsearch log messages on debug level
> 
> > > > > - Other installed Elasticsearch or Kibana plugins, if any
> 
> > > > >
> 
> > > > > Elasticsearch.yml:
> 
> > > > > ```auto
> > > > > searchguard.enterprise_modules_enabled: true
> > > > > 
> > > > > searchguard.ssl.transport.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > > > > searchguard.ssl.transport.pemkey_filepath: CN=emailnow.info.key.pem
> > > > > searchguard.ssl.transport.pemkey_password: $$$$$$$$$$$$$$$$$$
> > > > > searchguard.ssl.transport.pemtrustedcas_filepath: chain-ca.pem
> > > > > searchguard.ssl.transport.enforce_hostname_verification: false
> > > > > 
> > > > > searchguard.ssl.http.enabled: true
> > > > > searchguard.compliance.history.internal_config_enabled: true
> > > > > searchguard.compliance.history.external_config_enabled: true
> > > > > searchguard.compliance.history.read.metadata_only: true
> > > > > 
> > > > > searchguard.ssl.http.pemcert_filepath: CN=emailnow.info.crtfull.pem
> > > > > searchguard.ssl.http.pemkey_filepath: CN=emailnow.info.key.pem
> > > > > searchguard.ssl.http.pemkey_password: $$$$$$$$$$$$$$$$$$$$$$
> > > > > searchguard.ssl.http.pemtrustedcas_filepath: chain-ca.pem
> > > > > searchguard.allow_unsafe_democertificates: true
> > > > > searchguard.authcz.admin_dn:
> > > > > - CN=sgadmin
> > > > > 
> > > > > searchguard.audit.type: internal_elasticsearch
> > > > > searchguard.enable_snapshot_restore_privilege: true
> > > > > searchguard.check_snapshot_restore_write_privileges: true
> > > > > searchguard.restapi.roles_enabled: ["sg_all_access"]
> > > > > cluster.routing.allocation.disk.threshold_enabled: false
> > > > > cluster.name: searchguard_demo
> > > > > network.host: 0.0.0.0
> > > > > discovery.zen.minimum_master_nodes: 1
> > > > > node.max_local_storage_nodes: 3
> > > > > xpack.monitoring.enabled: true
> > > > > xpack.graph.enabled: false
> > > > > xpack.ml.enabled: false
> > > > > xpack.security.enabled: false
> > > > > xpack.watcher.enabled: false
> > > > > 
> > > > > ```
> 
> > > > > I have set the https for elastic search and Im able to access the elastic search from server and through curl. But Unable to access it from browser and getting the below exception.
> 
> > > > >
> 
> > > > > ```auto
> > > > > {"error":{"root_cause":[{"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"}],"type":"security_exception","reason":"no permissions for [cluster:monitor/main] and User [name=sg_anonymous, roles=[sg_anonymous_backendrole], requestedTenant=null]"},"status":403}
> > > > > 
> > > > > ```