-
Bug
-
Resolution: Fixed
-
Medium
-
4.0, 5.3.1, 5.4, 5.4.2
-
Confluence 4.0 beta 2, JIRA 4.4#649-r158309, Linux Mint 11, PostgreSQL 8.4.8
During post-installation of Confluence 4.0 beta 2, there is an option to load users from an existing JIRA installation. Attempting to do this causes setup to hang. I cannot proceed and cannot escape this screen, even after restarting the service. I see the little spinning circle I am told that less than a second elapsed endlessly. It does say:
"Local administrator account created.
We have created a local administrator with the same username and password as the JIRA system administrator you provided. This will ensure that you can always log into Confluence to update the system configuration."
The next button is visible but cannot be clicked.
If I refresh the page I get one of the following next to the spinning circle (in no particular order): "Synchronisation completed successfully.", "Synchronisation started.", and "embedded.crowd.directory.caching.sync.full"
I noticed something else odd - in JIRA, on the Configure Other Applications screen. I had created an application named "confluence" with IP address ::1, 127.0.0.1 and the actual IP address of my machine. This had worked find with Confluence 3.5. However after setting up Confluence 4.0 beta 2 there is a new application here with the following application name:
"Confluence - localhost - c2f77bbd-57fe-3852-bda6-8bfc6c0cdca9"
The only IP address on that is the real IP address, it doesn't have the local addresses. I tried adding these and restarting confluence (from init.d) but it didn't help.
I have confirmed this is not a problem with Confluence 3.5 (though this is post-setup in that version). I have tried recreating the confluence database and deleting the application data - this allows me to run through setup again but it hangs at the same place.
Workaround:
- In Chrome right click the greyed out button and select 'Inspect'
- The HTML should read:
<input class="aui-button aui-button-primary" id="nextButton" type="submit" value="Next >>" disabled="disabled">
- Remove the disabled attribute so it will looks like:
<input class="aui-button aui-button-primary" id="nextButton" type="submit" value="Next >>">
- The Next button will be enabled for the next page.
- has a regression in
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[CONFSERVER-23184] Setup hangs loading users from JIRA
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
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!
Jason Stone
added a comment - - edited 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! 
Jason Tan
added a comment - 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.
Jason Tan
added a comment - 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. 
Teun Segers
added a comment - Thanks Slawek Ginter! Just altering the HTML did it for me. Ridiculous bug. Definitely not resolved!
Teun Segers
added a comment - Thanks Slawek Ginter! Just altering the HTML did it for me. Ridiculous bug. Definitely not resolved!
https://jira.atlassian.com/browse/CONF-23184?focusedCommentId=424239&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-424239 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.
Christian Lerrahn
added a comment - - edited 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 error occured today running Confluence 6.7 on Docker 18.02.0, workaround provided worked on Firefox 58.0.2.