# \[FileBeat\] Unable to get X-Pack Monitoring to work

**URL:** <https://discuss.elastic.co/t/filebeat-unable-to-get-x-pack-monitoring-to-work/239721>\
**Category:** Beats\
**Tags:** elastic-stack-monitoring\
**Created:** [July 3, 2020, 1:41am UTC](https://discuss.elastic.co/t/filebeat-unable-to-get-x-pack-monitoring-to-work/239721 "2020-07-03T01:41:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vcc](https://avatars.discourse-cdn.com/v4/letter/v/977dab/32.png) [@vcc](https://discuss.elastic.co/u/vcc)\
**Post date:** [July 3, 2020, 1:41am UTC](https://discuss.elastic.co/t/filebeat-unable-to-get-x-pack-monitoring-to-work/239721/1 "2020-07-03T01:41:38Z")

</div>

Hi All,

I'm running into an issue getting X-Pack Monitoring to work with file beat. The setup we have is as follows:

- Elasticsearch Nodes have security enabled (using self signed certificates via elasticsearch-certutil)
- File Beat is running on a windows 10 PC
- Machine running file beat is behind a proxy server (WinGate)
- File Beat version is 6.8.10 (64 bit)

The following is the X-Pack Monitoring config portion of our File Beat config:

```auto
    #============================== Xpack Monitoring =====================================
    xpack.monitoring.enabled: true
    xpack.monitoring.elasticsearch:
      hosts: ["https://ca-yvr-app5:9200", "https://ca-yvr-app10:9200", "https://ca-yvr-app12:9200", "https://ca-yvr-app17:9200"]
      username: "beats_system"
      password: "password"
      proxy_url: http://172.16.0.2:3128
      ssl.enabled: true
      ssl.verification_mode: none

```

With the above config, it seems like there is an issue connecting to X-Pack Monitoring due to the `ssl.verification_mode: none` not being applied as the Wire Shark Trace seems to indicate that Handshake failed due to a bad certificate.

However, if we set the "proxy\_url" to use https instead the File Beat logs seem to indicate the `ssl.verification_mode: none` setting is applied, but with the call not being routed correctly through to the proxy as https is not supported.

Is there anyway to get around this issue? or is it simply just a configuration error on my end?

Thanks,  
Vincent

---

<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:** [July 31, 2020, 3:41am UTC](https://discuss.elastic.co/t/filebeat-unable-to-get-x-pack-monitoring-to-work/239721/2 "2020-07-31T03:41:52Z")

</div>

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