Getting a spinning wheel and an error popup:
"Unable to communicate with server. Saving is not possible at the moment."
Confluence status page shows no issues:
Not sure of the timing on this, but there were issues yesterday "Between 15:17 UTC to 16:14 UTC". That may be what you were experiencing.
Right, issue was fixed by itself.
That was definitely not a local problem as there are several other complaints about the same issue during the same period of time from other users in the forums.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As Kate mentioned above, I see this when I fail to save a page before disconnecting from ethernet connection and connecting to VPN or vice-versa. Sometimes it is a lag in our network connectivity. We run Confluence Server, so our issue is usually local.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here, our team faces this error and similar ones many times while trying to publish the pages. It happens frequently and one time we had to make a copy from the page in order to edit and publish.
This happens after the new confluence update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My 2 cents about a local cause for this problem - this happens to me frequently when connected to a VPN. I have learned to disconnect from the VPN when I expect to be heavily using Confluence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a very annoying error indeed.. Have had a few times myself (renewing the page usually solves it for me, even while you're editing all your content is saved every few seconds anyway). Sadly 'Unable to communicate with server' can mean a lot of things, especially on Cloud, seeing as there are many factors that can cause such communication problems.
If there weren't any status issues according to Atlassian, it might have been a more local problem for you. Did your colleagues have the same problem? Are you still having the problem now? My guess would be some kind of hitch on your computers connection, or the local network maybe?
Of course Atlassian is also not perfect. If you encounter such issues and you can be sure it's not a local issue, definitely just send in a ticket!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.