# Issue with metricbeat kibana module when using custom path for Kibana
**URL:** https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976
**Category:** Beats
**Tags:** metricbeat
**Created:** [July 22, 2023, 12:47am UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976 "2023-07-22T00:47:42Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Pierig\_Le\_Saux](https://discuss.elastic.co/u/Pierig_Le_Saux)
#### Post date: [July 22, 2023, 12:47am UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/1 "2023-07-22T00:47:42Z")
My kibana setup uses
```auto
SERVER_PUBLICBASEURL = http://www.example.com/kibana
SERVER_BASEPATH = /kibana
SERVER_REWRITEBASEPATH = "true"
```
My metricbeat autodiscovery for the kibana module uses:
```auto
- condition:
contains:
kubernetes.annotations.app: kibana
config:
- module: kibana
hosts: ["https://${data.host}:5601/kibana"]
```
But I am getting this in my metricbeat logs:
```auto
Error fetching data for metricset kibana.cluster_rules: invalid character '<' looking for beginning of value
```
As if metricbeat is hitting some HTML.
I can curl
[https://www.example.com/kibana/api/status](https://www.example.com/kibana/api/status) just fine.
I can also curl the pods ip directly from inside the cluster:
[https://elastic:elastic@10.150.1.22:5601/kibana/api/status](https://elastic:elastic@10.150.1.22:5601/kibana/api/status)
Before modifying the Kibana path, metricbeats was pulling Kibana metrics normally.
---
### Author:  [@PodarcisMuralis](https://discuss.elastic.co/u/PodarcisMuralis)
#### Post date: [July 22, 2023, 10:02pm UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/2 "2023-07-22T22:02:17Z")
Please try this.
```auto
hosts: ["https://${data.host}:5601]
```
And restart metricbeat. I hope it helps.
---
### Author:  [@Pierig\_Le\_Saux](https://discuss.elastic.co/u/Pierig_Le_Saux)
#### Post date: [August 1, 2023, 12:50pm UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/3 "2023-08-01T12:50:43Z")
Sorry this does not work:
> hosts: ["https://${data.host}:5601]
> Error fetching data for metricset kibana.cluster\_rules: HTTP error 404 in : 404 Not Found
Sorry for the late reply, I was out on holidays for a week.
---
### Author:  [@AJ\_Stack](https://discuss.elastic.co/u/AJ_Stack)
#### Post date: [August 4, 2023, 10:11am UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/4 "2023-08-04T10:11:34Z")
Try without the (S) in your https. Use http and see it this works.
---
### Author:  [@Pierig\_Le\_Saux](https://discuss.elastic.co/u/Pierig_Le_Saux)
#### Post date: [August 5, 2023, 1:30am UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/5 "2023-08-05T01:30:47Z")
I have tls enabled in kibana.
Metricbeats is able to upload dashboards to kibana fine to
https://${KIBANA\_HOSTS}:5601/kibana
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 2, 2023, 3:31am UTC](https://discuss.elastic.co/t/issue-with-metricbeat-kibana-module-when-using-custom-path-for-kibana/338976/6 "2023-09-02T03:31:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.