Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,776
Community Members
 
Community Events
176
Community Groups

License update "XSRF check failed"

Bitbucket could not complete this action due to a missing or expired form token.

You may have cleared your browser cookies, which could have resulted in the expiry of your current form token. A new form token has been issued.

The original input has been captured and you can retry the operation.

Any file attachments in the original input will be lost

 

We have an evaluation license that just expired and get the above message when trying to update to the new eval license.    We have a proxy server/load balancer in front and have not had any issues with BitBucket until now.   Looking at this: https://confluence.atlassian.com/stashkb/xsrf-security-token-missing-529661980.html  It appears our bitbucket.properties file is correct and we also have sticky session set on the load balancer.    Any ideas would be wonderful.

1 comment

Hi Jennifer,

This error typically appears when there's reverse proxy server in front of Bitbucket Server, but the bitbucket.properties file doesn't reflect that.

Specifically you need to make sure your bitbucket.properties file has the server.proxy-port and server.proxy-name and they match the port and FQDN of the URL you use to access Bitbucket Server.

For instance, if you access Bitbucket Server using https://bitbucket.company.com you'd need to set server.proxy-port=443 and server.proxy-name=bitbucket.company.com.

After a restart of Bitbucket Server you should be able to change your license.

Cheers,

Christian

Premier Support Engineer

Atlassian

Hi,

server.proxy-port and name are both in the properties file. we also have server.scheme=https   

Like Robert_Booke likes this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events