Same error occured today running Confluence 6.7 on Docker 18.02.0, workaround provided worked on Firefox 58.0.2.

Just a heads up in case you are trying this using this workaround in a newer version of Chrome that won't let you right click and inspect. You can copy and paste the URL into Firefox and do the workaround without losing any progress.

This issue is actually being handled in CONF-31129, and has been resolved in the 5.4.3, which will be the next bugfix release of Confluence. There is no scheduled date for the release currently, but we expect it to be within the next few weeks.

Please watch that bug report for further updates.

-Denise
Atlassian Support

This issue still occurs in v 5.4.2

Could someone please explain to me how to go about removing the disabled attribute for the next button. Downloaded Firebug and figured it out. Lol pretty ridiculous workaround, but it worked! Used Slawek Ginter's solution. Thanks a lot!

Another confirmation of this issue:

• CentOS 6.4
• JIRA 6.1.1. installer
• Confluence 5.3 installer

After installing JIRA on a clean system first, this issue popped up when running through the Confluence installer and choosing to load users from JIRA. Slawek Ginter's workaround was needed to complete the installation process.

FYI, just ran into the same issue when deploying JIRA/Confluence on the same CentOS box (latest binaries). Had to use the Firebug workaround.

I had the same problem and this seems to have something to DNS. In my setup, JIRA and Confluence both live on the same server which is a NAT-ed VM. When accessing the server's name from within, the name is resolved to the external IP which my setup cannot route correctly.

It seems that while I can override the DNS with a hosts file for the connection to resolve the name to the NAT-ed IP address, the synchronisation still queries the DNS server at soime point. Using an IP address did not work for me, either, possibly because JIRA uses a different base URL. The way to resolve this is to set up a local DNS server which resolves the FQDN of the machine to the IP address in the NAT-ed network.

So, if your JIRA server is called jira.example.com on the public IP address 123.45.6.7 but Confluence can only reach it on 192.168.1.10, you will need to set up a DNS server for your Confluence machine which resolves jira.example.com to 192.168.1.10.

@Slawek: Your solution most likely results in the synchronisation never finishing. I achieved the same at first by just reloading the page and somehow getting an active "Next" button.

Workaround I just used:

• I had an admin user which was neither "admin" nor "administrator" in JIRA as the only user
• I had the problem described above when setting up confluence
• I added "admin" and "administrator" because I suspected it's a "keep syncing until you see a well-known admin user" (sorry Connie guys, I know you would never do such thing )
• as this didn't help I used my Firebug to just remove "disabled" attr from the Next button and clicked it

Seems to have worked - saw the Welcome to Confluence page.

Same story
+1 to reopening

Same issue with 4.3.3 on Win 2008 r2.

No error about sync.

I too am seeing this trying to finish the setup wizard on Confluence 4.3.3, with the latest version of JIRA installed on the same system, both using the "Install from File" procedures. JIRA is running in the included standalone Tomcat container on its default port 8080, and I did not modify Confluence's default port 8090. Any help would be deeply appreciated.

I've tried to view the wizard in every major browser type, (as some other bug reports indicated some success doing so), but no luck so far.

It should be noted that in <confluence home dir>/logs/atlassian-confluence.log, I am seeing the following error message:
ERROR [Long running task: Synchronising JIRA Directory] [crowd.embedded.hibernate2.HibernateUserDao] addAll Please try to resolve any errors with these users, and try again.

No luck researching that one so far, either.

I've got the same problem with Confluence 4.3.3 - Standalone installed on Ubuntu 12

Updated fix for version to 4.0.3 which is available for download:

http://www.atlassian.com/software/confluence/ConfluenceDownloadCenter.jspa

Would it be possible to update the Fix Version so we know what version this will be in. My Director won't let me install into production with this defect/workaround.

Wayne,

As I see this is marked resolved I begin to wonder why it occurred from a download made today.

The issue has been fixed in an upcoming release, the version available on our website still has the problem.

I have experienced this as well and applied the same fix as Michael Cutler and Alexander Kanevskiy.

Problem appeared in Firefox, MSIE, and Chrome.

My Install is: CentOS 6 / JDK 6_27 / MySQL 5.1.52

As I see this is marked resolved I begin to wonder why it occurred from a download made today.

I have the same problem. The workaround worked.

The only thing is that the Example Site wasn't loaded so it seems like that step was skipped by using the workaround.

Please try the following workaround to resolve this issue.

Workaround

1. Please confirm that the following lines appear on atlassian-confluence.log

   [Long running task: Synchronising JIRA Directory] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache full synchronisation complete in [ (time)ms ]
   

   Do not apply the workaround if the lines is not on your atlassian-confluence.log (<Conf_Home_Dir>/logs/atlassian-confluence.log).

2. If its appear, please modify your confluence.cfg.xml (<Conf_Home_Dir>/confluence.cfg.xml) and modify the following lines. Backup your confluence.cfg.xml before modifying

   <setupStep>complete</setupStep>
   

3. Restart Confluence and try to logging into Confluence using JIRA user as Confluence internal user is disabled

The same problem persists in version 4.0 released on September 15th, 2011. Did anyone find a solution to this?

I've just had the same problem, fresh CentOS 6.0 virtual machine. Confluence standalone installed using "atlassian-confluence-4.0-x64.bin", told it to import Users from JIRA (and gave it an admin account). Whatever I did (restart VM, restart Confluence) it got stuck in the same state as the screenshots above.

WORKAROUND:

Using the "Firebug" plugin for Firefox I edited the "Next >>" button to removed the "disabled" attribute (same as Alexander Kanevskiy) then clicked the button and installation completed successfully.

Same here. Fresh installation of Jira v4.4.1#660-r161644 and Confluence 4.0 on a windows host. Got to the same state as Confluence showing "import complete" message with Next button grey. I selected in Chrome element inspector, removed disabled="disabled" from "Next" button properties, and clicked it. Installation finishes fine then. So should be trivial, that this attribute for some reason not removed from Next button after successful import of users from Jira.

Same issue here with 4.0 final release. Jira 4.4.1.

Added my Confluence log file. The last entry is 20 minutes old and Confluence is still hanged as described.

Same issue here, using the latest Confluence 4.0-rc7 and JIRA 4.4.1, running on Ubuntu 11.04 x64 with MySQL database. I'd suggest increasing the priority to Major (at least), because this issue prevents users from accessing Confluence and there seems to be no easy workaround once it happens.

Same Issue here. Nothing interesting in the log file.

I have the same issue here, using Confluence 4.0-rc3 and JIRA (v4.4#649-r158309). I tried it on Windows 7 (64 bit) and Ubuntu 11.04 (64 bit).

Also, I am able to set up JIRA as a user directory post-setup (configuring the "other application" in JIRA manually).

I should note I already requested support on this issue (CSP-67685), however the problem could not be resolved.