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

Updating Bamboo Specs from repository failed

I have added a Java specs project to an existing repository under the bamboo-specs subdirectory.  Once I merged this into master this triggered Bamboo to scan, e.g. I see a line in the Specs status tab on the relevant linked repository, but Specs status is "Error in Bamboo Specs"


I see the following error in atlassian-bamoo.log

2018-11-05 08:23:27,429 INFO [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-5] [BitbucketServerRssStatusUpdater] Sending RSS notification to Stash (repository: ...)
2018-11-05 08:23:31,598 INFO [15-BAM::SpecsDetection:pool-23-thread-1] [RssDetectionRunnable] Exception while executing RSS detection for repository 2359297
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Expected authority at index 7: http://
at com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl.generateBambooYamlsFromSpecs(


I don't see anything obviously relevant in atlassian-bitbucket.log


Both Bamboo and Bitbucket sit behind an apache reverse proxy providing HTTPS so I suspect this is the root cause of the issue.  Please advise on how to configure this correctly.

1 answer

This KB should get you all details needed to secure your connection behind an Apache reverse Proxy:

It's thought to be used for all Atlassian applications, so it's suitable for Bamboo and for Bitbucket.

Hope this helps, Jon.

Cheers, Gerhard

I'm able to access both Bamboo and Bitbucket using the https reverse proxy urls and they are functional as in I can create a plan manually which is triggered from a commit to one of our repos.  It's the specs scan specifically which does not work.

Hi Jon,

I found this resolved bug ticket for you:

Sound like what you're facing. I'm not sure what Bamboo version you use. If below 6.3.0, please consider a Bamboo upgrade.

Otherwise your case seems to be a bit more complex and we'd need more details from you for which best is to open a support case. Describe your situation there incl. your environment (Bamboo version, on what OS, inside Docker?, on same box as Bitbucket / other repo, etc.) and preferribly directly attach your Bamboo Support Zip.

Thanks, Gerhard

I created with a - FYI the UX on your attachment upload is poor, it's non-obvious that a file has been uploaded, hence you get the support zip 6 times...

I've been told that I am ineligible to create a support case.  Can you please create a bug report to track this.

Hi Jon, I could create a bug ticket if we knew that it is a bug.

I cannot reproduce your issue not using two reverse Proxies and encrypted (SSL) connections on both ends. Do you see a chance, just for test purpose, to bypass the Proxies and also go without SSL?

If this works, next, please follow these steps to get Bamboo run behind Apache using https: and see if this works.

If so, continue to to configure Bitbucket with Apache and SSL, like this:

One more idea: Do you you use https and not http for the Proxy URLs?

Hope this brings us further.

Cheers, Gerhard

Hi Gerhard,

I believe the bitbucket examples are stale as we are running 5.14.1 as per

It looks like server.scheme was missing from - I am waiting for a restart to confirm if that makes a difference.

I'm afraid this is still failing after adding server.scheme

Looking at your stack trace it seems to me that wherever the proxy string is being built it's not including the scheme ( - seems to be pulling in jersey.config.client.proxy.uri)

I can't really dig much further without access to your source.

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

223 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