I have tried to setup webhooks in bitbucket for one of my domains.
After setting up the webhook I performed a test. I cloned one of my repos from bitbucket to my local pc.
I changed something in the code of the file named 'testfile.php'. Of course I saved the file. After that I added the altered file to git with 'git add testfile.php' and issued the commit with 'git commit -m "Test"'. Last step was to push the repo back to bitbucket with 'git push origin master'.
When I logged in to Bitbucket, to check if the webhook was working, I saw this message
Content-Encoding | gzip |
Transfer-Encoding | chunked |
Server | nginx |
Connection | keep-alive |
Date | Fri, 18 Jan 2019 22:22:13 GMT |
Content-Type | text/html; charset=UTF-8 |
So it seems to be an 403 error (Forbidden)
I suppose it has something to do with certificate validation.
The website on https://example.com, which I created the webhook for, has a LetsEncrypt certificate.
I uploaded a lot of public ssh-keys to my Bitbucket repo's, because I access my projects from different devices.
Do you think that the output of my webhook test, has something to do with certificate validation? If so what steps should I take to issue the webhook successfully?