# Certificate error when watcher tries to notify slack

**URL:** <https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [May 12, 2017, 4:46pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600 "2017-05-12T16:46:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kamlesh\_Pandey](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@Kamlesh\_Pandey](https://discuss.elastic.co/u/Kamlesh_Pandey)\
**Post date:** [May 12, 2017, 4:46pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/1 "2017-05-12T16:46:31Z")

</div>

I am using elasticsearch 5.3.2 with watcher enabled. I created a sample watcher alert with slack webhook action. When I run the \_execute api on the alert it gives below SSL error response in the action section.

"actions": [  
{  
"id": "slack",  
"type": "webhook",  
"status": "failure",  
"reason": "SSLHandshakeException[sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]; nested: ValidatorException[PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]; nested: SunCertPathBuilderException[unable to find valid certification path to requested target]; "  
}  
]

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [May 15, 2017, 9:14pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/2 "2017-05-15T21:14:31Z")

</div>

Hey,

can you try and run your Elasticsearch instance with a recent oracle JDK and see if this problem persists? I have seen openjdk installations missing well known SSL root certificates causing this error and I would like to rule this out first.

Thanks a lot!

--Alex

---

<div class="post-metadata">

**Author:** ![bhayani\_sohil](https://avatars.discourse-cdn.com/v4/letter/b/57b2e6/32.png) [@bhayani\_sohil](https://discuss.elastic.co/u/bhayani_sohil)\
**Post date:** [June 6, 2017, 6:28pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/3 "2017-06-06T18:28:42Z")

</div>

Hi,

I am getting the same error, were you able to resolve it?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [June 7, 2017, 6:53am UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/4 "2017-06-07T06:53:24Z")

</div>

Hey,

I wrote possibilities above to try and resolve this. Did you try switching your JDK to an oracle one?

--Alex

---

<div class="post-metadata">

**Author:** ![Kamlesh\_Pandey](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@Kamlesh\_Pandey](https://discuss.elastic.co/u/Kamlesh_Pandey)\
**Post date:** [June 27, 2017, 7:09pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/5 "2017-06-27T19:09:10Z")

</div>

Hi All,

We were using exclusive certificates for ssl connections from our elasticsearch cluster. So I had to add slack certificate as a trusted certificate in my certificate bundle.

There is one more setting in xpack to just ignore ssl cert validation. Bit risky but you can try it

---

<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 25, 2017, 7:09pm UTC](https://discuss.elastic.co/t/certificate-error-when-watcher-tries-to-notify-slack/85600/6 "2017-07-25T19:09:11Z")

</div>

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