Webhook resulting in -2

[Chris Picard]

All of a sudden my webhooks started failing. When I turned on history, it said Network Error and has a status code of -2. I searched the documentation and it says a -1 is a timeout, but I can find no reference to what a -2 HTTP status code means.

[Patrick Theys _Opus_]

Same here. My failing webhook has skip_cert_verification set to true, while another one that is still working has it set to false. Maybe a certificate validation error?!

[Chris Picard]

I do also have the skip_cert_verification set to true and when I switched it to false the webhook worked. When I turned it back on right back to -2. My endpoint now does have valid certs so it seems like if you have it set and a valid cert, they changed something that now causes this error.

[Ben]

Hi @Chris 

Our engineering teams are currently investigating this issue. Can I confirm that now the error is no longer being caused?

And @Patrick Theys _Opus_ may you please try disabling Skip cert validation from Repository Settings > Workflow > Webhooks and observing what happens when triggering webhooks after doing so? What then happens when you re-enable it?

Cheers!

- Ben (Bitbucket Cloud Support)

[Patrick Theys _Opus_]

Thanks @Ben ,

It's working again.

[Ethan wang]

Same problem. All webhooks failed due to a network error (-2) since last Friday(29 May).
Firewall, IP whitelist, and WAF settings have been checked, and my webhook endpoints are working correctly (office network calls are working), but the problem persists.
Nothing was changed. It suddenly recovered this morning, possibly due to a Bitbucket malfunction.