Confluence is not allowing editing/saving some pages.

Question

Hi Team,

Since a couple of days, confluence is malfunctioning. It is showing different error every time when we try to edit and save a page. It also is not allowing creating pages in a few spaces.

"Unable to communicate with the 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"

"Something went wrong after loading the editor. Copy your unsaved changes and refresh the page to keep editing."

I have copied a few errors we found in our logs.

ff:fe44:8272%eth0, 10.41.104.98] and local port 5801

2020-02-06 10:15:42,610 INFO [Catalina-utility-1] [confluence.cluster.hazelcast.HazelcastClusterManager] startCluster Starting the cluster.

2020-02-06 10:15:55,231 WARN [Catalina-utility-1] [hazelcast.aws.utility.RetryUtils] log Couldn't connect to the AWS service, [1] retrying in 1 seconds...

Any help is greatly appreciated! :)

Please note that we recently upgraded both Confluence & JIRA on a suggestion from Atlassian Support Team member in a previous ticket.

Shannon S · Answer

Hi there,

Thank you for bringing this to us.

You can try first that your network allows WebSockets by running this test online:

* https://websocketstest.com/

Mostly this issue is a network issue, so you can also speak to your network administrator and make sure that the cause is not due to a firewall , VPN, or proxy. You'll want to try bypassing the proxy or try without the VPN/firewall connection to see if you're still able to publish.

The two messages you sent aren't error messages. The first one is an informational message during startup, and the second is a warning telling you that there was a brief connection issue that may have since been resolved. Errors will start with ERROR instead of INFO or WARN and will include a line at the end of the stack trace that says Caused by and will let you know the cause of the error.

If you continue to have issues, you can then trigger a save again, tail your Confluence Server logs, and you will eventually encounter the error message that is causing your issue. If you have any trouble, feel free to raise a new ticket with the Support team and we can have a look at your logs.

Regards,

Shannon