Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-44335

Edit/Create pages is not working when migrate from Cloud to Server

      Steps to Reproduce:

      1. Install a fresh Confluence 5.10.7
      2. Restore a Cloud Backup
      3. Create / Edit pages

      Actual behavior:

      Page spinning forever and following error appears in logs:

      2016-10-13 09:36:57,463 ERROR [http-nio-8090-exec-10] [confluence.plugins.synchrony.SynchronyContextProvider] getContextMap This instance could not be registered with Synchrony.
       -- space: 1638403 | url: /plugins/editor-loader/editor.action | page: 26705975 | traceId: 0d013bf225cda166 | userName: sysadmin | referer: http://localhost:8090/pages/viewpage.action?pageId=26705975 | action: editor
      

      Expected Behavior:

      Since you can restore cloud backup into 5.10 and later (here) you should be able to edit and create pages

      Workaround for Confluence 5.10):

      1. Navigate to <base URL>/admin/darkfeatures.action
      2. Remove:
        1. site-wide.synchrony
        2. site-wide.synchrony.opt-in
        3. site-wide.shared-drafts

      Workaround for Confluence 6.0+:

      This issue does not affect customers on Confluence 6.0 or greater. If you are experiencing issues editing pages after upgrade, please see Troubleshooting Collaborative Editing

            [CONFSERVER-44335] Edit/Create pages is not working when migrate from Cloud to Server

            Do we have any solution for Confluence 6.+ version?

            Daniel Ruiz added a comment - Do we have any solution for Confluence 6.+ version?

            I'm having this problem on the latest version of the software on the sever solution

            Ibukun akintokun added a comment - I'm having this problem on the latest version of the software on the sever solution

            I have latest version and I'm getting same thing on hosted solution

            fmelendez@metlifestadium.com added a comment - I have latest version and I'm getting same thing on hosted solution

            In my case removing all the features and adding only the synchrony related ones solved my problem.

            Gustavo Aguiar added a comment - In my case removing all the features and adding only the synchrony related ones solved my problem.

            Could someone provide some details on the workaround? Will removing the elements from darkfeatures disable Synchrony?

            Logan Hawkes added a comment - Could someone provide some details on the workaround? Will removing the elements from darkfeatures disable Synchrony?

            I am also seeing the issue. I am in the midst of an upgrade from server 5.8.8 to datacenter 6.2.3.

            Logan Hawkes added a comment - I am also seeing the issue. I am in the midst of an upgrade from server 5.8.8 to datacenter 6.2.3.

            I see this same problem when migrating from Cloud to Confluence Data Center, latest version 6.2.3 (also 6.2.2 and 6.2.1).

            Gustavo Aguiar added a comment - I see this same problem when migrating from Cloud to Confluence Data Center, latest version 6.2.3 (also 6.2.2 and 6.2.1).

            Mark Benson added a comment - - edited

            Hey Adam,

            FYI this error still occurs when importing an Atlassian Cloud Confluence backup > Confluence Server 6.2.1 (if it makes a difference - hosted in AWS using RDS Postgres DB)

            1. site-wide.synchrony
            2. site-wide.shared-drafts

            These values were both present and had to be removed manually.

            Mark Benson added a comment - - edited Hey Adam, FYI this error still occurs when importing an Atlassian Cloud Confluence backup > Confluence Server 6.2.1 (if it makes a difference - hosted in AWS using RDS Postgres DB) site-wide.synchrony site-wide.shared-drafts These values were both present and had to be removed manually.

            As Confluence 6.0 is now available, this should be the target version if migrating from Cloud to Server.

            If for some reason it is necessary to migrate to 5.10, please follow the workaround detailed in the description.

            Adam Barnes (Inactive) added a comment - As Confluence 6.0 is now available, this should be the target version if migrating from Cloud to Server. If for some reason it is necessary to migrate to 5.10, please follow the workaround detailed in the description.

              Unassigned Unassigned
              sparsa Saleh Parsa (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: