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
4,298,337
Community Members
 
Community Events
165
Community Groups

Reason of Error "Public Sign up is not enabled" while importing XML-Backup?

I've tried to import a XML-Export. After unzipping the Import-file the import stops with the following error message: 

{"errorType":"PublicSignUpDisabled","message":"Public Sign up is not enabled"}

 

Is there any special authorization requiered? How can i fix the error?

The XML file is from another confluence instance. Can this be the reaseon for?

 

Thanks!

David

3 answers

1 accepted

2 votes
Answer accepted
Lenard Lee Atlassian Team Oct 05, 2021

Hello @Aurelien Meunier , @David Heunisch !

 

During an XML import, this particular error message can appear if the user doing the import is not a "Site Admin". Can you check if that is the case, and if so, adding the user doing the import to the "Site admin" group should resolve this problem.

Hello @Lenard Lee

Thank you for your reply! That works for me! Thank you very much!

Indeed, that works for me too. However, I find this very puzzling, why would I see the Import feature if I can't do it?

Lenard Lee Atlassian Team Oct 14, 2021

Hi @Aurelien Meunier ,

Space Import is designed to be something a Confluence Admin can do. This specific error message, "PublicSignUpDisabled" happens because this Space Import process was also trying to create additional users. This is where the site admin permission is also needed.

Though, I suppose an improvement can be made to return a more descriptive error message :)

After a bit of testing on single page exports, it seems that this error is being thrown because the old system has user ID's that do not exist in the new system. One work around would be that you can modify the XML to remove users that no longer exist and replace their unique ID with someone that does exist in the new system. NOTE - This will mess up Confluence's revision history and comments as Confluence show changes/comments associated with the wrong user. It's easiest to test this by exporting/importing 1 single page to make sure it works. We were able to get this working for us, but does take a bit of work to get this done for the entire space XML which is very large and not easy to use a text editor with. 

Otherwise, I would expect you would need to create the same users in each system for the XML export/import to work normally. I didn't try this. 

Makes sense. I'll try that, thanks @Sean Seifert 

You can also empty the value of atlassianAccountId in the XML file (<property name=”atlassianAccountId”><![CDATA[]]></property>). The content will then be attributed to “Former user (deleted)”.

Same problem here, same scenario.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

179 views 1 3
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