We have a Bitbucket Data Center cluster behind a load balancer. When users clone over SSH, the Bitbucket logs see the IP address as the load balancer rather than the user. This is because TCP connections don’t allow a header to forward the client IP and instead just use the load balancer IP. This is troublesome when inspecting the access logs and not being able to associate a user to their IP address.
We have the option of adding the client IP to the TCP packet but Tomcat cannot parse the whole packet without changes being made. Does anyone have a workaround so we can see where our SSH requests are coming from?
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events