Atlassian We ve Encountered a Problem Please Try Again in a Few Minutes

Summary

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

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

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

Surround

Confluence Server or Data Center
Release 6.x or greater

Cause

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

Resolution

Step #i - Access 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 Admission URL will result in users unable to edit any pages. Please ensure that this has been checked off the listing. Please take annotation of the protocol (http or https) that Confluence is using. Go toConfluence Admin > Full general Configuration to check Confluence's Base of operations URL:

Step #2 - Restart Synchrony

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

Later on, endeavor to create a new page or edit an existing one and see if the issue is resolved. If non, continue to the side by side step.

Footstep #3 - Check to Encounter 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: gyre -i http://localhost:8091/synchrony/heartbeat

The results should be the text OK

If this fails, bank check the following:

- Is the Collaborative Editing disabled netherConfluence Assistants » General Configuration » Collaborative Editing?
- Is the java Synchrony process running?
  - Windows : bank check the Details tab of the Confluence process in Task Manager
  - Linux: ps -ef | grep -i synchrony.cadre | grep -vi grep
- IsSynchrony listening on the port it is binding on?

Stride #4 - Review proxy configuration (If applicable)

At that place is additional configuration that must be done inside the proxy configuration file in lodge to make information technology work with Collaborative Editing. Below is the relevant documentation you can use for reference:

- How to utilize NGINX to proxy requests for Confluence

Note that changing the files mentioned in either of the KBs to 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 have configured your reverse proxy, but tin can't edit pages, here are some things to cheque in your configuration:

Go toinstallation-directory>/conf/server.xml and check theConnector directive. Make certain that you have right values for<protocol> and<proxyName>. See the examples in the guides above for more data. Note that these are case sensitive.
If you're using Apache, check the order of the Confluence and Synchrony directives and location blocks in the proxy config file. See the examples in the guides above for more information.
If you're using Apache, make certain y'all're using Apache 2.four (with WebSockets support) and all required modules accept been enabled (modernistic-proxy,mod_rewrite,proxy_wstunnel).

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

Proxy, SSL, and any network configuration is not part of our back up scope as per Atlassian's Back up Offerings. Any effort provided to back up issues related to proxy or SSL configuration will exist on a best-endeavour basis by the support engineer.

Step #v - Forward proxy configuration (If applicative)

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

If you're using Confluence 6.0 or later on with Synchrony, y'all'll demand to pass the post-obit to ensure Confluence tin connect directly to Synchrony. Replace localhost|127.0.0.1 with your Synchrony IP if you have used the synchrony.host system property to modify the IP Synchrony uses.
              -Dhttp.nonProxyHosts=localhost\|127.0.0.1 -Dhttps.nonProxyHosts=localhost\|127.0.0.i            

Information technology is insufficient to include just localhost as the IP address 127.0.0.1 needs to exist explicitly defined. These changes are either made in your system property or they can be establish in catalina.properties - depending on where you defined them. Restart Confluence after making these changes and observe to meet if the issue still persists.

Step #6 - Enable safe mode

While Collaborative Editing is ready to On, enable safety style and run into if the upshot persists. This way, we can eliminate third-political party add-ons as one of the possible causes of the issue.

Enabling safe way will disable all of your user-installed add-ons at one get. It is a good troubleshooting method to determine if an issue is acquired by a third-political party addition or non. If it is, you lot can likewise easily place which i is the culprit past enabling them one by one and observing when the upshot occurs again.

Afterwards, try to create a new page or edit an existing one and run into if the issue is resolved. If not, proceed to the steps beneath where applicable.

Step #7 - Turning off Collaborative Editing and Contacting Support

Get together the following to provide to support:

Details of whatsoever networking configuration that Confluence is running on, with its configuration files.
Generate a HAR filewhile replicating the outcome with the editor not loading or page not saving. This will capture all requests and responses between the browser and server.
Create a full Support Aughtso that we can cross check the logs with the requests and timestamps contained in the HAR file.

If this is occurring in your production environment, Switch off Collaborative Editing temporarily in social club to ensure your users tin continue using the wiki site as per normal. Refer to Administering Collaborative Editing for full documentation of this feature and its modes.

Apply this as atemporary workaround for the fourth dimension being to minimize disruption to your business organization processes. Turning Collaborative Editing off falls dorsum the editing and saving mode to what it was in Confluence v.ten.

To disable it, Navigate toConfluence Administration > General Configuration > Collaborative Editing > Change fashion 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
Besides many people in the editor

Notes

Equally a all-time practise, it'southward recommended to accept a staging environment that is divide and identical to your production environment on which nosotros can practise troubleshooting on. This is so we can ensure minimal disruption to your production, as all changes are kickoff applied to your staging environment.