Collaborative Synchrony Something Went Wrong Please Try Again

Summary

After a new installation or an upgrade to Confluence, users are no longer able to edit whatever pages. The following error messages may appear in a pop-upwardly error dialog:

            Loading the editor's taking longer than usual. Requite it a few moments, and then refresh your page if it withal doesn't load. Speak to your Confluence admin if that doesn't fix it.          

            This folio is taking longer to load than usual. Requite it a few moments, then try refreshing. Yet having issues? Contact your Confluence admin.          

Environment

• Confluence Server or Data Heart
• Release half-dozen.ten or greater

Cause

The Synchrony process that enables Collaborative Editing is unreachable by the end-user'due south browser.

Resolution

Step #1 - Admission URL and base URL match

With Collaborative Editing in place, it is very important to ensure that both the access URL and server base URL of the instance are identical. A mismatch of Base URL and Access URL will consequence in users unable to edit any pages. Please ensure that this has been checked off the list. Please accept note of the protocol (http or https) that Confluence is using. Go toConfluence Admin > General Configuration to check Confluence's Base URL:

Step #2 - Restart Synchrony

Navigate to Confluence Assistants > Full general Configuration > Collaborative Editing and click on "Restart Synchrony".

Afterward, effort to create a new folio or edit an existing one and see if the consequence is resolved. If non, proceed to the next step.

Step #iii - Check to Run into if Synchrony is Running and Accessible locally

• For Window Server instances, open up http://localhost:8091/synchrony/heartbeat in a browser on the server

• For Linux distributions run: curl -i http://localhost:8091/synchrony/heartbeat

The results should be the text OK

 If this fails, check the following:

• • Is the Collaborative Editing disabled underConfluence Administration  » General Configuration  » Collaborative Editing?
  • Is the java Synchrony  process running?
    
    • Windows : cheque the Details  tab of the Confluence procedure in Task Manager
      
    • Linux: ps -ef | grep -i synchrony.core | grep -vi grep
  • IsSynchrony listening on the port it is binding on?

Step #4 - Review proxy configuration (If applicable)

There is boosted configuration that must be washed within the proxy configuration file in order to make it piece of work with Collaborative Editing. Below is the relevant documentation you lot can apply for reference:

• • How to use NGINX to proxy requests for Confluence

 Note that irresolute the files mentioned in either of the KBs in a higher place requires a proxy restart. Pay special attention to the sections that are specifically for Confluence 6.

Here's a quick proxy troubleshooting checklist provided in this documentation: Troubleshooting Collaborative Editing

If you lot accept configured your reverse proxy, just can't edit pages, here are some things to cheque in your configuration:

• Get toinstallation-directory>/conf/server.xml and check theConnector directive. Make certain that you have correct values for<protocol> and<proxyName>. Meet the examples in the guides above for more data.   Note that these are case sensitive.
• If you're using Apache, check the society of the Confluence and Synchrony directives and location blocks in the proxy config file. See the examples in the guides in a higher place for more than information.
• If you're using Apache, make sure yous're using Apache 2.iv (with WebSockets support) and all required modules accept been enabled (mod-proxy,mod_rewrite,proxy_wstunnel).

If you are not using a reverse proxy, and tin can't utilise Confluence's internal Synchrony proxy for some reason, please make sure port 8091 is open up and available for Synchrony to use (or change the port that Synchrony runs on).

 Proxy, SSL, and any network configuration is non office of our support scope as per Atlassian's Back up Offerings. Any endeavor provided to support issues related to proxy or SSL configuration will be on a all-time-effort basis past the back up engineer.

Step #5 - Forrard proxy configuration (If applicable)

In Confluence 6 onwards, we need to explicitly include 127.0.0.1 equally function of the http.nonProxyHosts and https.nonProxyHosts setting to ensure Synchrony can piece of work properly. This is mentioned in our documentation Configuring Web Proxy Support for Confluence:

If you're using Confluence 6.0 or later with Synchrony, you lot'll need to pass the following to ensure Confluence can connect straight to Synchrony. Supervene upon localhost|127.0.0.ane with your Synchrony IP if you take used the synchrony.host arrangement property to change the IP Synchrony uses.

              -Dhttp.nonProxyHosts=localhost\|127.0.0.1 -Dhttps.nonProxyHosts=localhost\|127.0.0.1            

It is insufficient to include just localhost as the IP address 127.0.0.1 needs to be explicitly divers. These changes are either made in your system property or they can be constitute in catalina.properties - depending on where y'all defined them. Restart Confluence after making these changes and observe to see if the outcome however persists.

Pace #6 - Enable condom mode

While Collaborative Editing is set to On,  enable safe way and see if the consequence persists. This mode, we tin eliminate third-party add-ons as one of the possible causes of the issue.

 Enabling safe mode volition disable all of your user-installed add-ons at one go. It is a skilful troubleshooting method to determine if an issue is acquired by a 3rd-political party addition or not. If information technology is, yous can likewise easily identify which i is the culprit by enabling them one by ane and observing when the issue occurs again.

Afterwards, try to create a new page or edit an existing one and meet if the issue is resolved. If not, continue to the steps below where applicable.

Stride #7 - Turning off Collaborative Editing and Contacting Support

Gather the post-obit to provide to back up:

1. Details of any networking configuration that Confluence is running on, with its configuration files.
2. Generate a HAR filewhile replicating the upshot with the editor non loading or page not saving.  This will capture all requests and responses between the browser and server.
3. Create a full Support Naughtso that we can cross cheque the logs with the requests and timestamps independent in the HAR file.
   

If this is occurring in your production surroundings, Switch off Collaborative Editing temporarily in order to ensure your users tin can continue using the wiki site every bit per normal. Refer to Administering Collaborative Editing for full documentation of this feature and its modes.

Utilise this as atemporary workaround for the time being to minimize disruption to your business processes. Turning Collaborative Editing off falls back the editing and saving mode to what it was in Confluence 5.ten.

To disable information technology, Navigate toConfluence Administration > General Configuration > Collaborative Editing > Modify mode and select "Off". After changing modes, all users should be able to edit and create new pages at present.

Other common issues

Other common issues that contribute to Collaborative editing issues are:

• Port 8091 is unavailable
• Websocket issues
• Memory issues
• Multiple Synchrony processes
• Incompatible browser extensions 
• Too many people in the editor

Notes

As a best practice, information technology's recommended to have a staging surround that is carve up and identical to your production surroundings on which we can do troubleshooting on. This is and so we can ensure minimal disruption to your production, every bit all changes are beginning applied to your staging environment.

christoffersocort1957.blogspot.com

Source: https://confluence.atlassian.com/display/CONFKB/Unable+to+edit+any+pages+in+Confluence+due+to+Collaborative+Editing

Share this post