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

[Ian Carson]

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
                </Proxy>

                ServerAdmin dev@domain.com
                ServerName pipe.domain.com

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

                SSLEngine On

                SSLCertificateFile /etc/apache2/ssl/star.domain.com.crt
                SSLCertificateKeyFile /etc/apache2/ssl/star.domain.com.key

                SSLCertificateChainFile /etc/apache2/ssl/star.domain.com.ca-bundle
        </VirtualHost>

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

                <Connector
                                protocol="HTTP/1.1"
                                port="8085"

                                maxThreads="150" minSpareThreads="25"
                                connectionTimeout="20000"
                                disableUploadTimeout="true"
                                acceptCount="100"

                                enableLookups="false"
                                maxHttpHeaderSize="8192"

                                useBodyEncodingForURI="true"
                                URIEncoding="UTF-8"

                                secure="true" SSLEnabled="true" sslProtocol="TLS"
                                proxyName="pipe.domain.com"
                                redirectPort="443"
                                scheme="https"
                                proxyPort="443"
                />

[Ian Carson · Accepted solution]

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

[Steffen Opel _Utoolity_]

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?

[Ian Carson]

My base URL is the same as pipe.domain.com. Is that incorrect?

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

[Steffen Opel _Utoolity_]

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:

• https://pipe.domain.com/
• https://pipe.domain.com/bamboo

[Ian Carson]

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.

[Ian Carson]

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

[Ian Carson]

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.

[Steffen Opel _Utoolity_]

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!

[Ian Carson]

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.

[Steffen Opel _Utoolity_]

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

[Steffen Opel _Utoolity_]

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 my.atlassian.com/license/evaluation.