Typically when we see these kinds of errors in the application, it happens because your environment has some mechanism to redirect traffic to bitbucket, like a reverse proxy, a firewall, or a port forwarding/redirect rule.
Bitbucket can work with these kinds of setups, but in order to do so, we need to make sure that the bitbucket site itself is configured to understand that its traffic is being served up on another site/address.
I would recommend walking through the KB Cross Site Request Forgery (CSRF) protection changes in Atlassian REST. It walks through better diagnosing this error and provides steps on how to resolve this. With Bitbucket 5.x you will likely need to make these changes in the
<Bitbucket home directory>
/shared/bitbucket.properties file, save these, and then restart the application in order for these changes to take effect.
Please let me know if you have any questions or concerns about the steps in that KB.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs