# Elasticsearch can't execute watcher due to hooks.slack not being resolved

**URL:** <https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [September 24, 2020, 2:36pm UTC](https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835 "2020-09-24T14:36:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cctk](https://avatars.discourse-cdn.com/v4/letter/c/73ab20/32.png) [@cctk](https://discuss.elastic.co/u/cctk)\
**Post date:** [September 24, 2020, 2:36pm UTC](https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835/1 "2020-09-24T14:36:06Z")

</div>

I Have elasticsearch v7.9.1  
Kibana v7.9.1  
unfortunately the watchers have stopped working after I set up x-pack security.  
I cannot curl [hooks.slack.com](http://hooks.slack.com) , this is my result.

`curl -v https://hooks.slack.com`

```auto
* Could not resolve host: hooks.slack.com
* Closing connection 0
curl: (6) Could not resolve host: hooks.slack.com

```

I have added a new Webhooks to elasticsearch keystore and the elasticsearch.yml file looks like this.

```auto
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.http.ssl.verification_mode: none

xpack.watcher.enabled: true
xpack.notification.slack:
  account:
    monitoring:
       message_defaults.from: Kibana
       message_defaults.icon: true

```

and the keystone url is : `xpack.notification.slack.account.monitoring.secure_url`

Theses are the errors I get in elasticsearch.log is:

```auto
[ERROR][o.e.x.w.n.s.SlackService] [node-1] failed to execute slack api http request
ERROR][o.e.x.w.n.s.SlackService] [node-1] failed to execute slack api http request

```

can anyone help me with this issue.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 28, 2020, 3:53am UTC](https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835/2 "2020-09-28T03:53:34Z")

</div>

Tried this on my laptop;

```auto
~ curl -v https://hooks.slack.com
* Trying 52.63.104.105...
* TCP_NODELAY set
* Connected to hooks.slack.com (52.63.104.105) port 443 (#0)

```

Sounds like you may have a DNS issue in your network, rather than an Elasticsearch issue.

---

<div class="post-metadata">

**Author:** ![cctk](https://avatars.discourse-cdn.com/v4/letter/c/73ab20/32.png) [@cctk](https://discuss.elastic.co/u/cctk)\
**Post date:** [September 28, 2020, 9:19am UTC](https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835/3 "2020-09-28T09:19:44Z")

</div>

yes it was a DNS problem. thank you

---

<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:** [October 26, 2020, 9:19am UTC](https://discuss.elastic.co/t/elasticsearch-cant-execute-watcher-due-to-hooks-slack-not-being-resolved/249835/4 "2020-10-26T09:19:50Z")

</div>

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