# 'Webhook callback failed: 400 Client Error' when using autodeploy

**URL:** <https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011>\
**Category:** Docker Hub\
**Tags:** automatedbuilds, dockerhub, build\
**Created:** [April 25, 2016, 12:42pm UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011 "2016-04-25T12:42:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eamonwoortman](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/eamonwoortman/32/8633_2.png) [@eamonwoortman](https://forums.docker.com/u/eamonwoortman)\
**Post date:** [April 25, 2016, 12:42pm UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/1 "2016-04-25T12:42:43Z")

</div>

Hey there,

When using the Docker Registry’s webhook to deploy a service on Docker Hub, i’m getting the following output/error:

> 

Service Redeploy (trigger) action on ‘web’ (using ‘my\_organization/my\_repository:latest’) has finished successfully  
Webhook callback failed: 400 Client Error: BAD REQUEST for url: [https://registry.hub.docker.com/u/my\_organization/my\_repository/hook/hookhash2raf2frafaf/](https://registry.hub.docker.com/u/my_organization/my_repository/hook/hookhash2raf2frafaf/)

While the deployment was a success, Docker Cloud could not successfully use the webhook callback, resulting in an error for the notification services(like Slack).

The request was made to:

> POST /api/app/v1/service/service\_hash/trigger/trigger\_hash/call/

I’m not really sure what to do, it looks like a bug at your end.

Let me know if you require more information.

With kind regards,

Eamon Woortman

---

<div class="post-metadata">

**Author:** ![alifa](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/alifa/32/10400_2.png) [@alifa](https://forums.docker.com/u/alifa)\
**Post date:** [May 26, 2016, 7:34am UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/2 "2016-05-26T07:34:17Z")

</div>

I have same problem, did you manage to fix this?

---

<div class="post-metadata">

**Author:** ![eamonwoortman](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/eamonwoortman/32/8633_2.png) [@eamonwoortman](https://forums.docker.com/u/eamonwoortman)\
**Post date:** [May 26, 2016, 2:40pm UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/3 "2016-05-26T14:40:26Z")

</div>

Sorry, it’s still not working. Manual redeploys do report fine to Slack but the triggered webhook still fails to perform the callback.

---

<div class="post-metadata">

**Author:** ![robertavram](https://avatars.discourse-cdn.com/v4/letter/r/46a35a/32.png) [@robertavram](https://forums.docker.com/u/robertavram)\
**Post date:** [June 20, 2016, 7:53pm UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/4 "2016-06-20T19:53:47Z")

</div>

+1 … I’m having the same issue… Docker Cloud trigger

---

<div class="post-metadata">

**Author:** ![walterpinson](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/walterpinson/32/11849_2.png) [@walterpinson](https://forums.docker.com/u/walterpinson)\
**Post date:** [June 28, 2016, 6:47am UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/5 "2016-06-28T06:47:12Z")

</div>

++1 …I’m experiencing the same with Docker Cloud trigger.

---

<div class="post-metadata">

**Author:** ![eamonwoortman](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/eamonwoortman/32/8633_2.png) [@eamonwoortman](https://forums.docker.com/u/eamonwoortman)\
**Post date:** [June 28, 2016, 12:54pm UTC](https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/6 "2016-06-28T12:54:58Z")

</div>

Update:

So the _webhook callback_ is still failing as shown in these timeline entries:

```auto
[6/28/2016, 2:33:38 PM]web-1: Creating in NODE_HASH.node.dockerapp.io with docker name CONTAINER_NAME
[6/28/2016, 2:33:39 PM]web-1: Starting with docker id CONTAINER_ID in NODE_HASH.node.dockerapp.io
[6/28/2016, 2:33:40 PM]web-1: Running in NODE_HASH.node.dockerapp.io
[6/28/2016, 2:33:40 PM]Service Redeploy (trigger) action on 'web' (using 'mycompany/myimage:latest') has finished successfully
[6/28/2016, 2:33:40 PM]Webhook callback failed: 400 Client Error: BAD REQUEST for url: https://registry.hub.docker.com/u/mycompany/myimage/hook/HOOK_HASH/

```

However, the _Slack notification bot_ is now sending ‘success’ messages, instead of failures, which is sufficient in my case.

![](https://global.discourse-cdn.com/docker/original/2X/6/63666d6375cebf55f366efc9ef69983fd31785d1.png)