Bamboo doesn't recognise repository address when fronted by a proxy server

One common method of putting a proxy-server in front of a Java appserver is to use mod_proxy. However, when using mod_proxy the connecting IP address is proxying host (often 127.0.0.1), which breaks triggers as the connecting host won't match the repository host. Note that this will also apply where other forms or proxies (load-balancers, client caching proxies) are in place.

One option is to inspect the headers for the 'X-Forwarded-For:' header, which contains the IP of the original connecting host. The longer term (probably correct) option is to use HTTP-basic auth instead of IP filtering.