# Handshake... ERROR x509: certificate signed by unknown authorityhandshake

**URL:** <https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 11, 2023, 11:27am UTC](https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741 "2023-04-11T11:27:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![songhe](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@songhe](https://discuss.elastic.co/u/songhe)\
**Post date:** [April 11, 2023, 11:27am UTC](https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741/1 "2023-04-11T11:27:25Z")

</div>

**version:7.17.9**

**filebeat command** ：filebeat test output  
elasticsearch: [https://10.202.250.243:9200](https://10.202.250.243:9200)...  
parse url... OK  
connection...  
parse host... OK  
dns lookup... OK  
addresses: 10.202.250.243  
dial up... OK  
TLS...  
security: server's certificate chain verification is enabled  
handshake... ERROR x509: certificate signed by unknown authority

**/etc/filebeat/filebeat.yml**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/e/4efea8445bf10fd6b3783bc992810394d5ac592a.png)

**/etc/elasticsearch/elasticsearch.yml**

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/2/d2ccd36169da495a9aa3ff4561002c31a687ac9b.png)

---

<div class="post-metadata">

**Author:** ![TimBosman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timbosman/32/84120_2.png) [@TimBosman](https://discuss.elastic.co/u/TimBosman)\
**Post date:** [April 11, 2023, 1:43pm UTC](https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741/2 "2023-04-11T13:43:49Z")

</div>

Hey welcome on the forum.

I think you can resolve this by setting `output.elasticsearch.ssl.certificate_authorities` or `output.elasticsearch.ssl.verification_mode: none` in the Filebeat.yml see [the documentation here](https://www.elastic.co/guide/en/beats/filebeat/7.17/configuration-ssl.html#server-verification-mode). In production, I would recommend using the first option.

Tim

---

<div class="post-metadata">

**Author:** ![songhe](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@songhe](https://discuss.elastic.co/u/songhe)\
**Post date:** [April 20, 2023, 6:06am UTC](https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741/3 "2023-04-20T06:06:34Z")

</div>

thank you for your reply, i decide renew some certificates for instance.yml。maybe it is useful

---

<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:** [May 18, 2023, 8:07am UTC](https://discuss.elastic.co/t/handshake-error-x509-certificate-signed-by-unknown-authorityhandshake/329741/4 "2023-05-18T08:07:16Z")

</div>

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