Webook HTTP status -2

[Mark Kabana]

Have had a webhook setup for years that has been working fine on the repo:push action.

A few weeks ago the webhook started failing with HTTP status -2

Nothing changed and can't find any reason why this is happening.

There is no documentation available for this error.

We have simulated sending the request to our server using Postman with no issues.

So issue is with Bitbucket server sending webhook.

Can someone from the Bitbucket team please let us know what this error means and how to resolve?

Thanks!

[Theodora Boudale]

Hi Mark,

A few weeks ago we made changes that affected the list of TLS Ciphers supported by webhook requests:

• https://bitbucket.org/blog/updated-list-of-tls-cipher-suites-for-webhook-requests

If your webhook started failing around the same time, you may be affected by this change.

You can find the list of supported cipher suites here:

• https://support.atlassian.com/security-and-access-policies/docs/supported-security-protocols-for-atlassian-cloud-products/#Supported-cipher-suites

Could you please review the web server's configuration and ensure it is configured to support one of the supported ciphers?

Kind regards,
Theodora

[Jimmy.Diep]

Try enabling the logs for the webhook

repos -> repository settings -> webhooks -> view request logs

[Mark Kabana]

I have the request logs enabled...by viewing the log entries this is how i am able to tell that the HTTP Status is -2 - have no idea what a -2 status code means...

Any other ideas?