Webhook failed with status code 503

Configuration
1

I tried to use the ios shortcuts but it failed with “Error during api.callService” Code 503.

In the app under debug i can see the “Webhook failed with status code 503”.

What am i am doing wrong?

Thank you,

Stefan

1 Like
2

Same issue. I cannot get the external url in iOS to take now. It worked fine before a few HA updates.

3

And idea how to solve that ?

4

Same here after latest update…

5

Same here and I am glad that it’s not me. I deleted and reinstalled the app with no change.
Any News out here?

6

Same issue here…cannot update - just fails with webhook 503 error.

7

Hey, just to let you know. I reset the app completely via “debug → reset” and that configured from scratch. That did the trick. Now my events are triggered just fine again.

2 Likes
8

Been seeing this issue for while.

Did a reset on all devices, and hit the same issues less than 12 hours later.

Seems like devices are keen to refresh their web hook IDs with many “deleted web hooks” populating the Configuration > Cloud page.

Any thoughts?

9

Hey, everyone. I was having this issue and banging my head against the wall, and then I figured out that it was happening because I had turned on “Bot Fight Mode” in my Cloudflare settings. Sounded like a good thing, but apparently blocks all bots, good and bad, unless you pay for the “super” version.

10

I encountered this exact issue.
Did you ever find a way to solve this? Did you end up turning off Bot Fight Mode? Or something else?

11

Same issue. Any solutions? Works on iPhone, but not on Apple Watch

12

If it works on the iPhone, then the connection between iPhone and Home Assistant works. Apple Watch is a dependent from the iPhone sub-system. So, it must not be related to the title problem “we hook failed with the status code 503”

13

I’ve created an explicit allow-all rule together with disabling the bot protection and it worked.

Interestingly that after I’ve removed the rule and enabled the bot-protection, it continued to work. Probably, related to something statistics-based bot detection.

Anyway “allow all rule” helps to watch ALL traffic in the CloudFlare logs and hopefully better understand what went wrong.