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

Cloud Migration Assistant for Confluence - enable fails


Confluence (on-prem) Server - 6.8.0

Cloud Migration Assistant for Confluence - 1.0.9

Plugin installs OK.

Plugin fails to enable.

Error message:

Error creating bean with name 'cloudSiteSetupService': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate []: No default constructor found; nested exception is java.lang.NoSuchMethodException:<init>()

5 answers

1 accepted

1 vote
Answer accepted

after working with confluence support it was determined that my okta (okta-confluence-3.0.6.jar) add-on was conflicting with the cloud migration add-on.

removing the okta add-on (restarting services, etc.) allowed my cloud migration add-on to enable.

Standalone confluence with installation in http://<public-ip>:8090 and no "wiki" or "confluence" at the end, did not allow enabling Migration Manager. In some deep logs there was mention of URL being missing from some bean constructor.

SOLUTION was to redefine confluence base-url in general configuration.

I just added "/" at the end so it became "http://<public-ip>:8090/" and saved it.

After that, I was able to enable Migration Manager.

My theory is, that base url was NOT set, but upon rendering general configuration, my IP and port were shown as default value (even though it was not saved in database), upon saving a change to it, that DB field got populated and resolved the missing URL error from within Migration Managers dependency.

Thanks Lauri, solved my problem!

I also had the problem that the Addons didn't enable. We could solve it with the help of the Atlassian Support. Our problem was that the Confluence Analytics System Addon was disabled. Don't ask me why but this blocked enabling the Cloud Migration Assistant.

Good day Diego,


I have also followed all of your suggested steps, yet non of them has been successful.
w.r.t the last step, after that, Confluence starts up, but as soon as I need to access any administration content, an "System Error" occurs. I have in the mean time, reverted back to a server snapshot i took, before attempting any of the steps suggested.

@Etienne Janse van Rensburg please see my accepted answer. I hope this helps you.

0 votes
Diego Atlassian Team Mar 22, 2019

Hello there Zac!

We can start by checking if the plugins cache are fine by clearing them and then trying to enable to plugin once more:

  1. Schedule a downtime for Confluence
  2. Remove the following folders:
    1. <confluence-home>/bundled-plugins
    2. <confluence-home>/plugins-cache
    3. <confluence-home>/plugins-osgi-cache
    4. <confluence-home>/plugins-temp
    5. <confluence-home>/bundled-plugins_language
  3. Start Confluence
  4. Click Cog Icon>General Configuration
  5. Search for Content Indexing in the left menu bar
  6. Click the Rebuild button

If the above yields no results, we can also try the following:

  1. Click cog icon > Add-ons
  2. Scroll down to the bottom of the page
  3. Click Enter safe mode
  4. Proceed to enter safe mode
  5. Now, enable just the Cloud Migration Assistance Plugin
  6. Check if the plugin actually enables

Now, we still have a third option here:

  1. Schedule a downtime for Confluence
  2. Uninstall the Cloud Migration Assistant for Confluence 
  3. Remove the following folders:
    1. <confluence-home>/bundled-plugins
    2. <confluence-home>/plugins-cache
    3. <confluence-home>/plugins-osgi-cache
    4. <confluence-home>/plugins-temp
    5. <confluence-home>/bundled-plugins_language
  4. Start Confluence
  5. Download the plugin directly from here:
    1. Cloud Migration Assistant for Confluence
  6. Install it via File Upload:
    1. Installing Marketplace apps | Installing by file upload
  7. Check if the plugin enables

Hey, I know that this can be quite a info at once but, could you clarify a few points for us:

  1. Are you able to enable or disable other plugins?
  2. Has the plugin worked at some point in the past?
  3. Which version of Java are you currently using in your environment?
  4. Is this your production instance?

Zac, looking forward to your reply!

Thank you for the reply.

A couple answers to your questions.

1. Yes, we have other plugins installed and enabled. I haven't attempted to enable/disable them recently. That is a good idea to test.

2. No, this is our first time working with this plugin.

3. java -version

java version "1.7.0_161"
OpenJDK Runtime Environment (rhel- u161-b00)
OpenJDK 64-Bit Server VM (build 24.161-b00, mixed mode)

 4. Yes, this is our production environment.

I need to schedule a downtime for confluence to work on the options you suggested.


This morning I had confluence downtime and attempted your suggested steps.

I still was not able to enable the plugin.

The error message in the logs stayed consistent throughout.

I did notice the link you provided was migration-agent-2.0.2.jar which was newer than then migration-agent-1.0.9.jar I was previously using. But it didn't seem to help. Same failure and error.

I answered your other questions in the previous reply.

Do you have any further suggestions?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events