GitLab.com: Web Hook returns error 500

Twitter: https://twitter.com/losthismind13/status/669158592193282048

Sunil

My web hooks aren't working any more. "Test Hook" gives 500 "Whoops, something went wrong on our end." message.

@DouweM

Is your Web hook returning a 200 status code?

Unfortunately still getting a 500 status code when I click "Test Hook"

Been almost a week and the issue is still there. Is there any information I can provide to you that will help you solve this issue? My Jenkins CI server is kind of useless without the web hook to trigger actions.

@spai I think what Stan meant was: Does you webhook work if you trigger it manually? (not from the gitlab GUI)
If it does, please provide some more information.
which version of gitlab are you running? did it work before? When did it break?

I'm using GitLab.com to host my repos. I am not running it locally.

Pretty sure that means I can only use the GUI to trigger the web hook.

It stopped working about a week ago.

@spai Please don't use @all. This just creates a lot of spam.

mentioned in issue #3530 (closed)

@spai You should be able to test your Web hook via some other method (e.g. curl). If your Web hook is serving via HTTP, you could always just use tcpdump or Wireshark to snoop on the HTTP traffic. You could always set up a local instance of GitLab too.

@jacobvosmaer, can you see if the logs show any Web hook errors for @spai?

I understand now. Yes, when I call the URL configured on my web hook outside of GitLab (command line, web browser, etc), I get a successful response. Only GitLab.com is returning a 500 error.

@stanhu If I leave the "SSL Verification" checkbox unchecked, the gitlab.com UI says the hook executed successfully. My webhook is an HTTPS URL with a registered certificate (not self-signed) so I don't know why SSL verification would cause an error.

@spai, are you sure your SSL certificate bundle has all the right intermediate certificates? You may want to check with this tool:

https://www.sslshopper.com/ssl-checker.html

You are correct. The certificate bundle contained the root and all intermediate certificates but it did not contain the site's certificate itself. Adding that to the chain file allows SSL Verification to work. Thank you for your help with this.

Is this not a bug/regression, then?

@rspeicher No, it is not. I do think we should catch the SSL verification error in TestHookService and report a more helpful message.

mentioned in merge request !1943 (merged)

Status changed to closed by commit a120b789

mentioned in commit a120b789

mine also returns 500 error