Upgraded Bamboo from 6.4.1 to 6.10.2
Carried over parms from previous server.xml file. No changes were made to proxy/apache server. Nothing really changed in the config files from the previous version. Not sure why only the view all deployment projects page is affected, everything else seems to be ok.
Everything looks ok except when trying to access Deploy > All Deployment Projects ... we get two pop-ups.
First - An unexpected error has occurred, Please try reloading page
Second - Background page refresh cannot contact server. Please ensure Bamboo server is available.
In the logs we see the following:
2019-12-09 15:31:36,740 INFO [https-jsse-nio-8085-exec-22] [AccessLogFilter] xaxg066 POST https://bamboo.grainger.com:5443/rest/api/latest/deploy/dashboard/status 7589620kb
2019-12-09 15:31:36,742 WARN [https-jsse-nio-8085-exec-22] [XsrfResourceFilter] Additional XSRF checks failed for request: https://bamboo.grainger.com:5443/rest/api/latest/deploy/dashboard/status , origin: https://bamboo.grainger.com , referrer: https://bamboo.grainger.com/deploy/viewAllDeploymentProjects.action , credentials in request: true , allowed via CORS: false
We have a work-around by adding the proxy port (5443) to the url - example
What doesn’t work anymore: https://bamboo.grainger.com/deploy/viewAllDeploymentProjects.action
<!-- Reverse proxy listening port -->
In case anyone else is here from google, I too ran smack into this upgrading to 6.10.4 (prior version I'm unsure - I had done multiple serial upgrades and didn't check the deploy page on each hop). My corporate security appliance shall remain nameless, but SSL terminates at the appliance, so Tomcat is getting http, but everything about Bamboo the app, has to be fooled into thinking it's https.
What I had to do to get this working was Admin > General Configuration> Base URL: https://bamboo.my.co/bamboo
Tomcat connector config: scheme="https" proxyName="bamboo.my.co" proxyPort="" secure="true"
That "" is not a mistake.
This config finally allowed that deploy page to finally compose the same origin and referrer URLs.
Prior to this upgrade, the tomcat config was simply (and, I guess wrongly) proxyName="bamboo.my.co" proxyPort="443"
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