We recently started a project of upgrading from Confluence v5.6 to v6.1.
We hit issues in the 6.1 version when trying to publish a new page:
"Unable to communicate with server. Saving is not possible at the moment."
"The editor didn't load this time.
The connection timed out. If it happens again, speak to your Confluence admin. You may be using a proxy server that prevents WebSocket connections."
We are using Firefox and addressing the base URL of the installation, not frontended by any web-server (Apache), no URL redirection.
I turned Collaborative editing into "Limited" and it seems to be working.
But we want to keep Collaborative editing activated.
Can you help ?
Please review the steps outlined in:
Also, check whether the following is in the <Confluence_Home>/confluence.cfg.xml file:
You may need to open a ticket at https://getsupport.atlassian.com so Support can investigate your logs. To include a support zip for the support team, please follow these instructions: Creating a support zip file It will include configuration files as well as logs to help them take a closer look.
Thank you for reacting on this.
We do have the following:
But to be honest, as we do not use any Apache or other webserver in front at this stage, but just accessing directly via http://<ServerName>:8090,
does this value really need to be set to "true" ?
It is for now, but it did not improve the reported behaviour.
Thank you for any further advice.
[by the way, we already opened this ticket:
I am confident your support engineer will get to the bottom of the issue. Please look at this diagram, it shows why I asked to have the synchrony proxy enabled: No reverse proxy
"If you don't run Confluence behind a reverse proxy, you'll connect to Synchrony via Confluence's internal Synchrony proxy. SSL, if used, is terminated at Tomcat. This is the default configuration, and you shouldn't need to make any additional changes to use collaborative editing."
Just saw on your ticket that the root cause was that Synchrony could not obtain a database connection until you added an argument to the synchrony-args.properties file.
If there is more about the case that you would like to share with the Community, feel free to update the thread in case it can help someone else.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs