I have been getting this error message every time I try to access the plugins. This also seems to stop any of the plugins from updating with the response. I have SSL setup through a proxy apache server.
XSRF check failed
# ProxyVia On
Allow from all
ProxyPass / http://localhost:8085/
ProxyPassReverse / http://localhost:8085/
I have tried to change the xml config multiple ways but nothing seems to work. This is my server.xml code
secure="true" SSLEnabled="true" sslProtocol="TLS"
Your configuration looks correct at first sight - I'm usually encountering this error when Bamboo's base URL is not set properly, see Specifying Bamboo's URL:
"This is the base URL of this installation of Bamboo. All links created (for links in Bamboo email notifications etc.) will be prefixed by this URL.
To specify Bamboo's URL:
This is easy to overlook, for example when restoring a backup - have you missed that eventually?
When I add a slash to the end of the url it just get's stripped out when I head back to the General Configuration screen.
I am mostly confused as to why my bitbucket instance does not have the same problems as bamboo does.
https://pipe.domain.com <= this is the domain format I used.
2017-07-18 01:00:54,658 INFO [http-nio-8085-exec-17] [AccessLogFilter] admin GET http://pipe.domain.com/rest/plugins/1.0/com.atlassian.upm.atlassian-universal-plugin-manager-plugin-key?_=42243432234432
2017-07-18 01:00:56,113 INFO [http-nio-8085-exec-5] [AccessLogFilter] admin GET http://pipe.domain.com/rest/plugins/1.0/com.atlassian.upm.atlassian-universal-plugin-manager-plugin/marketplace?_=24323324324432423
2017-07-18 01:00:56,783 INFO [http-nio-8085-exec-2] [AccessLogFilter] admin GET http://pipe.domain.com/rest/plugins/1.0/pac-details/com.atlassian.upm.atlassian-universal-plugin-manager-plugin/2.22.1?_=23442323243423
2017-07-18 01:00:57,079 INFO [http-nio-8085-exec-1] [AccessLogFilter] admin GET http://pipe.domain.com/rest/plugins/1.0/pending?_=234234423423423
2017-07-18 01:00:57,172 INFO [http-nio-8085-exec-8] [AccessLogFilter] admin POST http://pipe.domain.com/rest/plugins/1.0/?token=24324342343242423
2017-07-18 01:00:57,224 WARN [http-nio-8085-exec-8] [XsrfResourceFilter] Additional XSRF checks failed for request: http://pipe.domain.com/rest/plugins/1.0/ , origin: https://pipe.domain.com , referrer: https://pipe.domain.com/plugins/servlet/upm , credentials in request: true , allowed via CORS: false
You can see the logs here. The last warning was thrown when I tried to update a plugin.
The requests via http rather than https are odd indeed.
I've just cross checked your configuration with our own and it looks almost identical (except for us running Bamboo alongside other Atlassian products, therefore with a context and individual ProxyPass directives inside of resp. Location directives).
Unfortunately I'm not an Ops guru and need to pass now, sorry - if nobody else chimes in, I'd recommend to file a support request with Atlassian support, they should be more than willing to get a you going with Bamboo!
That would be understandable, however, I'm not aware of Atlassian refusing support to evaluators (to the contrary, they want to win you over as a customer after all) - have you tried to submit a technical support request via the contact form? While they require you to enter a 'Support Entitlement Number (SEN)', an evaluation license should do just fine (to the best of my knowledge, I'd really be surprised if that's not the case anymore).
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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