Webhook triggered from Bitbucket Server writes "failed with an error" to logs but no stack trace

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

Problem

If a webhook triggered from Bitbucket encounters a missing or invalid certificate issue, it throws an error but does not log a detailed stack trace.

The following appears in the atlassian-bitbucket.log

2019-03-26 12:08:34,097 INFO  [ForkJoinPool.commonPool-worker-2]  c.a.w.i.p.DefaultWebhookDispatcher Webhook invocation [50a10c86-3946-416c-bd04-b89f11526470] to [https://example.host/?token=9yaSaqa0dio31EdalX401WFtZO5DH2JJ] failed with an error

Cause

This error is due to a missing or invalid certificate on Bitbucket Server end for the target host, example.host.

Resolution

Import the certificate for target host, example.host, into Bitbucket Server trustStore as explained at How to import a public SSL certificate into a JVM.


Last modified on May 8, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.