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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
An SSL error occurred, please check that the provided resource uses https.
If you have any information which could help sort this issue would be great.
Thanks a lot for reading this issue and possible support in advance!
Hey @Helcio Mayor
Did you setup a valid SSL certificate for your Jenkins or is it self-signed certificate?
The best way to debug these kind of errors is to login to the the client machine (BitBucket) and make curl requests to the target machine (Jenkins).
Hope it helps.
Hi Thanks for your reply. No its not a self-signed. Sure, I have to know what message Jenkins is returning really.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also, does Jenkins https work from other machines/clients?
The answer to this question will help focusing your search: If you manage to connect to Jenkins https from different client - Look into the BitBucket webhooks setup. If no client manage to connect to Jenkins https, look into Jenkins https configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure and thanks! Yes I can connect from different clients using HTTPS. The webhook I am testing was created from Jenkins when I saved the multibranch setup which is what Jenkins does. I have used steps similar to Adding a certificate to Jenkins on Windows. - things from here and there (joeypiccola.com) to make Jenkins to use HTTPS (I use Windows). Slight different to convert keys as I had to use powershell. I am just wondering when the api call is from Bitbucket it may try to find certificate in another path.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.