Rally Webbooks erroring out when target URL is http (& potentially behind firewall)

[Raghavendra Kulkarni]

Hello @David LeDeaux or @Gregory Garcia or @Lenn Thompson

I have setup a Rally webhook for which a target url is http://... and it is behind my company firewall. I see from the webhook get call that webhook failed, errorcount increases by 1 and last http status is null. So, my question is below is there a way to get this working and more specifically

1) Does the target url in webhook need to be internet publicly available url or can it be behind firewall (like mine) but I can authenticate.
2)If I use the same url from Postman and post the same message (as Rally would in webhook), it works.

In summary, Rally webhook is not able to post the message to my target but I do webhook is getting triggered. Appreciate any help or guidance on this.

Regards,
Raghu​​​

[David LeDeaux]

The LastStatus attribute contains the HTTP response code, typically provided by the target web server.  So for that attribute to have a value, there is a requirement that the webhook is able to perform communication with the target web server.  That value being null implies that the webhook was never able to reach the target URL, perhaps due to the firewall you mentioned.

Are you able to access that target URL from outside of your network?  For example, if you are at home and not VPNed into your company network, can you still access that URL?

[Raghavendra Kulkarni]

Hi @David LeDeaux
Thanks for your quick answer. Sorry I am responding to my question but it is answering your question (since I didn't find any other reply button). No, I cannot access targetURL outside ​of my network. If I shut-off my VPN, I cannot access, If I turn on my VPN, I can.

However, http://rally1.rallydev.com/ is also kind of behind of firewall (not sure about it but guessing) because we use SSO to login. So, I thinking something behind firewall (like rally.rallydev.com thru SSO) should be able to access something behind firewall (like target URL)

Regards,
Raghu

[David LeDeaux]

We do have our own firewall, however that is independent of anything related to SSO or the firewall you may have at your organization.  The SSO trust isn't like a VPN where we would have internal access into your network.

In order to have this webhook communicate successfully, you would need your network team to open a port in your firewall to allow access to your target web server.
Additionally, if your target URL is an internal address like server5.company.local, we may not be able to determine the location of that server since it's also an internal address.

[Raghavendra Kulkarni]

Thanks @David LeDeaux Based on what you mentioned, the only option is network team has to open the port for Rally webhook to post. Can you let me know which port does Rally webhook post whenever a target url is given? ​

[David LeDeaux]

I would imagine that we default to 80 or 443 depending on whether you used HTTP or https respectively.
But, the port could be overridden in the target URL like https://server5.company.com:12345/targetendpoint

[Raghavendra Kulkarni]

That helps, thank you @David LeDeaux Appreciate your inputs/guidance. Have a good rest of the day!​