You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.