Bitbucket Webhooks with Proxy

[Andrew Gehring]

If we configure an inbound proxy (nginx), and set server.proxy-name|port, how do we get webhooks to provide the proxies URL?

[Charlie Misonne]

Hi Andrew and welcome to the Atlassian community!

server.proxy-name is for your inbound (reverse) proxy indeed. If your webhooks need to go through an outbound proxy that is totally unrelated.

Outbound proxies use the Java/JVM properties:

• http.proxyHost
• http.proxyPort (default: 80)
• http.nonProxyHosts (default: <none>)
• https.proxyHost
• https.proxyPort

You need to set these as JVM parameters in the_start-webapp.sh file if you're on Linux: 

JVM_SUPPORT_RECOMMENDED_ARGS="-Dhttp.proxyUser=atlaspirate -Dhttp.proxyPassword=yarrrrr -Dhttps.proxyUser=atlaspirate -Dhttps.proxyPassword=yarrrrr"

You can also set the environment variable in the systemd service on Linux.

And if you run it as a Windows service you need to set in it the java service settings.

More info on How to configure an outbound HTTP and HTTPS proxy for Bitbucket Server:

[Aokynse]

I was once trying to get my app to communicate with a third-party service, and the webhook URLs were all over the place. I figured out that I needed to make sure my proxy settings were correct to point to the right URL. Once I set the server.proxy-name|port, it really helped. I also found that using mobile rotating proxies made a difference in how I handled requests. They provided a new IP for each request, which kept things fresh and helped avoid any blocks. My webhooks started working more reliably, and the whole process became way smoother.