Webhook to Jenkins fails with "Network Error"

Question

Hi,

i am running a Jenkins Instance with Docker on a private Server (no firewall active, bute UFW running). I installed the plugin multibranch-scan-webhook-trigger and configured my job as described with token=commprom_angular_frontend. I can trigger the pipeline with the corresponding post method:

Everthing works fine.

I also configured the webhook in the corresponding bitbucket repository as follows:

But if i commit and push changes, every request will end up with a Network Error:

Details of this request:

The body of request looks fine.

Does anyone have an idea, why this happens? How can i have a deeper look into the logs of this requests?

Thanks a lot in advance and all the best!

Simon

unknown · Answer

Hey Mateus,

thanks for the input, we were able to resolve the issue on Friday. We were missing intermediate certificates in our Jenkins ssl setup.

Kind regards,

Lukas

Mateus T · Answer

Hi @[deleted],

Checking your Jenkins URL against an SSL analyzer, I was able to see that your certificate does have some issues making it not compliant and causing Bitbucket to refuse the connection. These were the issues I got:

jenkins.abeel.eu:8443: FAILED - Not compliant.
    * maximum_certificate_lifespan: Certificate life span is 393 days, should be less than 366.
    * ciphers: Cipher suites {'TLS_DHE_RSA_WITH_AES_128_CBC_SHA256', 'TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256'} are supported, but should be rejected.
    * dh_param_size: DH parameter size is 1024, should be superior or equal to 2048.

In this case, I'd check with your certificate providers to fix the issues mentioned above.

Cheers,

Mateus T

unknown · Answer

Hello @Mateus T ,
I find myself in almost the exact same situation as Simon. The webhooks only work when the 'Skip certificate verification' box is ticked. When we want the webhooks to verify our certificate we get the same error as in the opener of this discussion:

Now the difference to the original post is that we don't use a self signed certificate. I'm able to connect to Jenkins with the valid certificate through the browser and I'm able to call the webhook from Postman. Could you check to see where the validation fails?

If this is not the correct place to ask such a question you can happily refer me to the correct spot to do so.