Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

URL configuration of your instance does not match the URL in your browser

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

        <VirtualHost *:443>
                 ProxyPreserveHost On
                 ProxyRequests Off
#                ProxyVia On

                <Proxy *:*>
                        Allow from all


                ProxyPass       / http://localhost:8085/
                ProxyPassReverse / http://localhost:8085/

                SSLEngine On

                SSLCertificateFile /etc/apache2/ssl/
                SSLCertificateKeyFile /etc/apache2/ssl/

                SSLCertificateChainFile /etc/apache2/ssl/

 I have tried to change the xml config multiple ways but nothing seems to work. This is my server.xml code


                                maxThreads="150" minSpareThreads="25"



                                secure="true" SSLEnabled="true" sslProtocol="TLS"

2 answers

1 accepted

0 votes
Answer accepted

Path was the wrong directory. Was in the /opt/bamboo/atlassian-bamboo/conf/server.xml path instead of the proper path which was /opt/bamboo/conf/server.xml

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:

  1. Click the  icon in the Bamboo header and choose  Overview.
  2. Click General Configuration (under 'System'), in the left navigation panel.
  3. In the Base URL field, type the URL address of your Bamboo server (for example, "http://keg:8080/bamboo").
  4. Click Save."

This is easy to overlook, for example when restoring a backup - have you missed that eventually?

My base URL is the same as Is that incorrect?

(NOTE: that I don't have any sub path being used like /bamboo etc)

The URL must be syntactically complete, i.e. include the protocol and also the application server context in case you are using one, i.e. either one of these:


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. <= this is the domain format I used.

One odd thing is all the rest calls are in http instead of https. I have no idea why this is happening...

2017-07-18 01:00:54,658 INFO [http-nio-8085-exec-17] [AccessLogFilter] admin GET
2017-07-18 01:00:56,113 INFO [http-nio-8085-exec-5] [AccessLogFilter] admin GET
2017-07-18 01:00:56,783 INFO [http-nio-8085-exec-2] [AccessLogFilter] admin GET
2017-07-18 01:00:57,079 INFO [http-nio-8085-exec-1] [AccessLogFilter] admin GET
2017-07-18 01:00:57,172 INFO [http-nio-8085-exec-8] [AccessLogFilter] admin POST
2017-07-18 01:00:57,224 WARN [http-nio-8085-exec-8] [XsrfResourceFilter] Additional XSRF checks failed for request: , origin: , referrer: , 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!

Thanks for the help, my company is sadly not yet willing to invest in that support tier (we area on the starter plan) unless we can get the product working to test.

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).

Ah, I missed the 'Starter' plan bits - still I think and hope that evaluating with a larger license tier should be sufficient, just get youself a new one via

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

195 views 4 6
Read article

Community Events

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

Events near you