You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm running Jenkins version 2.369 with Bitbucket Push and Pull Request plugin version 2.8.3. I've got a webhook setup in Bitbucket to trigger a job in Jenkins.
When I do a commit to bitbucket, the plugin gets triggered, but the job on Jenkins does not run. When looking at the "View Requests" for webhooks in the Bitbucket UI, I see:
Response from https://18.104.22.168:8080/bitbucket-hook/
HTTP status: -2
I've not been able to find logs on the Jenkins controller to look at the HTTP traffic there, so I installed tcpdump. If I capture HTTP traffic on the controller I find this data showing a return from Jenkins to Bitbucket.
22:39:09.133202 IP <Jenkins-internal-AWS-ip>.webcache > 22.214.171.124.25366: Flags [P.], seq 1:206, ack 313, win 219, options [nop,nop,TS val 1282987750 ecr 2120152488], length 205: HTTP: HTTP/1.1 400 Bad Request
Lx..~^..HTTP/1.1 400 Bad Request
Bad Message 400 reason: Illegal character CNTL=0x16 (with some HTML formatting removed)
From this I see two problems:
Has anyone else run into this issue and know a resolution?
Thanks in advance,
Could you please let us know
I can then check the webhook logs for the repo and see if there is more information regarding the error.
Workspace ID is ric....
X-Event-Time Tue, 17 Jan 2023 01:10:57 GMT
X-Event-Time Fri, 13 Jan 2023 00:30:12 GMT
X-Event-Time Thu, 12 Jan 2023 22:56:55 GMT
Let me know if you need any other information, and thanks for your help,
Thank you for the info. The webhooks logs for this repo indicate an SSL related error.
I would suggest editing the webhook from Repository settings and temporarily checking the option Skip certificate verification for testing purposes, to verify if the webhook works without certificate verification. If it does, please check if there are any issues with the server's certificate.
Hello @Rick Martin !
The error being returned by the webhooks processor seems to be related to the TLS version being used on your Jenkins server.
It seems that during the TLS handshake, your Jenkins server is offering an old TLS version (TLSv1) that is not supported. You can refer to the blog post Update to supported cipher suites in Bitbucket Cloud for further details on the deprecated ciphers.
In this case, I would recommend checking if your Jenkins instance is using at least TLSv1.2. Also, since Jenkins is based on java, you might want to verify if your java version supports and is configured to use at least TLSv1.2
All the current supported ciphers are documented at Supported security protocols for Atlassian Cloud Products .
Thank you, @Rick Martin .