Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cannot start Bamboo due to pad block corrupted error


We cloned the database schema to a test instance.

Bamboo doesn't start afterwards because of the following error message:

FATAL [localhost-startStop-1] [BambooContainer] Cannot start bamboo java.lang.RuntimeException: org.bouncycastle.crypto.InvalidCipherTextException: pad block corrupted

Editing the bamboo-mail.cfg.xml as described at doesn't help.

Any idea how can we start Bamboo?

1 answer

1 accepted

1 vote
Answer accepted
Elias Zeidan (they/them)
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 19, 2018 • edited

Hi Andreas,

Thanks for reaching out to the Atlassian Community!

The "Pad block corrupted" error occurs when we're unable to correctly use the Bamboo Cipher. 

The Cipher is split between the database and filesystem, and the filesystem part is stored in


When you cloned the Bamboo database, did you also copy the Bamboo Home directory? If you did not, please:

  1. Stop Bamboo
  2. Copy the cipher.key_0 file from the original Bamboo instance to the clone into the correct directory – you may need to create the `<bamboo-home>/xml-data/configuration/cipher/cipher.key_x`
  3. Start Bamboo

Please let us know if this works, or if you have any other questions!


Elias | Bamboo Support

Hi Elias,

Thanks a lot for your quick reply!

That fixed the issue, Bamboo was able to start up after I copied the cipher.key_x from the cloned system.



Elias Zeidan (they/them)
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 20, 2018

Hi Andreas, 

I'm glad we were able to help you get back up and running!

Could you please "Accept" this answer by clicking on the checkmark symbol near my first comment in case other users might find this helpful?

Thanks again for reaching out. If you have any other questions, please do not hesitate to ask!

Elias | Bamboo Support

@Elias Zeidan (they/them) 

What if we miss that cipher?

Elias Zeidan (they/them)
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 10, 2021

Hi @cnp rayan ,

Thanks for your question.

For security reasons, if the cipher is missing Bamboo will not start under default configuration.

There is a system parameter that can be added to Bamboo to disable the encryption/decryption.

With this added Bamboo can start, but any data that had been encrypted previously will not be available. Depending on your version of Bamboo, this could include variables, Repository configurations, secrets, passwords, and more.

If you can, I would strongly encourage you to contact Bamboo Support for assistance with a restore.


Elias | Former Bamboo Support Engineer

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events