Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Description
Problem Definition
When using any reverse proxy eg. HAProxy, the client IP address is not logged in the access logs and we have to make changes to the proxy config to get that working by following https://confluence.atlassian.com/bitbucketserverkb/log-the-original-ip-address-when-bitbucket-server-is-behind-a-load-balancer-779171715.html
When deploying mmproxy especially the golang port of mmproxy with a staging instance we were able to successfully pass the origin address through to Bitbucket and have it clearly displayed in the access log.