# Merticbeat Error dialing x509: certificate is valid for 127.0.0.1, not 172.16.0.204
**URL:** https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323
**Category:** Beats
**Tags:** metricbeat
**Created:** [March 10, 2022, 10:47am UTC](https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323 "2022-03-10T10:47:02Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Spyros\_Agriopoulos](https://discuss.elastic.co/u/Spyros_Agriopoulos)
#### Post date: [March 10, 2022, 10:47am UTC](https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323/1 "2022-03-10T10:47:02Z")
Metricbeat has stopped working and is giving me Error dialing x509: certificate is valid for 127.0.0.1, not x.x.x.x after a yum update. Other instances that are using the exact same certificate are working fine. Any ideas?
```auto
# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
# Array of hosts to connect to.
hosts: ["x.x.x.x:9200"]
# Protocol - either `http` (default) or `https`.
protocol: "https"
ssl.certificate_authorities: ["/home/user/elastic/ca/ca.crt"]
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
username: "user"
password: "pass"
```
#### UPDATE
With older versions of metricbeat it works, is this a known issue?
---
### Author:  [@Marius\_Iversen](https://discuss.elastic.co/u/Marius_Iversen)
#### Post date: [March 10, 2022, 1:30pm UTC](https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323/2 "2022-03-10T13:30:10Z")
Did you perhaps upgrade from 7 to 8 for the metricbeat?
It does seem that the certificate is not valid for that host, and there might be more checks that has been added, from 8.0+ the Elastic stack has security enabled by default.
You can try to disable verification to see if it starts up as intended then? It's not a "fix" unless you are happy with having it disabled, but the complaint about the certificate missmatch seems correct.
See if you can set:
`output.elasticsearch.ssl.verification_mode: none`
---
### Author:  [@TiagoQueiroz](https://discuss.elastic.co/u/TiagoQueiroz)
#### Post date: [March 10, 2022, 3:19pm UTC](https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323/3 "2022-03-10T15:19:18Z")
> [@Spyros\_Agriopoulos](#):
>
> x509: certificate is valid
Yes, that's a know issue, but the fix has been merged to `main` a little while ago. There are some GitHub issues (and the fix PR):
- [Filebeat Loadbalance wrong cert validation · Issue #30240 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/30240)
- [[Heartbeat] Mixup of TLS certificates on multi-monitor configs · Issue #30290 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/30290)
- [tlscommon: fix race condition on TLS hostname validation by belimawr · Pull Request #30305 · elastic/beats · GitHub](https://github.com/elastic/beats/pull/30305)
Which version of Metricbeat are you running @Spyros_Agriopoulos. The fix has been released on [7.17.1](https://www.elastic.co/guide/en/beats/libbeat/7.17/release-notes-7.17.1.html)
There is also a simple workaround of setting `ssl.verification_mode: certificate`
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 7, 2022, 5:19pm UTC](https://discuss.elastic.co/t/merticbeat-error-dialing-x509-certificate-is-valid-for-127-0-0-1-not-172-16-0-204/299323/4 "2022-04-07T17:19:33Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.