Can't connect to the server

[Kendall Walker]

When I try to edit a page or create a new page in Confluence I get these error messages:

'Can't Connect to the server: Looks like your session expired. Log in again to keep working. Login'

'Unable to communicate with server. Saving is not possible at the moment'

'Error saving draft. No draft has been saved.

I have logged out and back in again twice.

JIRA is working without issues, just confluence is generating the errors. 

[Jesus Mondragon]

Did you get this resolved? How did you do it?

[Kendall Walker]

I checked the 'site status' page under the help menu and found this incase it helps anyone in future:

Confluence Cloud unable to save pages

Identified - We have identified the root cause. A recent change is causing Atlassian Connect macros to throw an error when executed and prevent pages from being saved. A fix is currently being prepared. 
Dec 8, 06:00 UTC

Investigating - Some Confluence Cloud instances are currently unable to save or update pages. 

Atlassian are currently investigating this issue as a high priority and further updates will be shared as more information becomes available. 
Dec 8, 05:54 UTC

image2016-12-8 14:33:4.png

[Dave Nurney]

Hi, we are running our own confluence server (i.e. not cloud )and also experience the same issues/error messages.

Do you have an update or time line for the fix please?

[Jesus Mondragon]

Same here. Any answers?

[Dave Nurney]

Nope not even an acknowledgement - may be it should be recorded as a new issue

[Kevin Deuel]

Hi All, has there been any updates to this yet?

we just upgraded to 6.2 and face the same issue with Collaborative Editing. 

We have a reverse proxy from:

http://confluence.companyname.com

Pointing to:

http://atlassian01.companyname.com:8090

Collaborative Editing works only if we go directly to http://atlassian01.companyname.com:8090

If we use http://confluence.companyname.com we get the same issue of Confluence kicking the user off the system.

[ABHISHEK]

After 6.1 version of Confluence you need to change proxy settings in server.xml file, please modify the server.xml file like below, hope you dont frustate it and dont getting any timeout.

 <Connector port="8090" connectionTimeout="20000" redirectPort="8443"
                maxThreads="48" minSpareThreads="10"
                enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
                protocol="org.apache.coyote.http11.Http11NioProtocol"
                proxyName="confluence.xyz.com" proxyPort="443" scheme="https"
                />

Please reply back if you still face that issue.

Thanks

[Kevin Deuel]

Hi Abhishek, we tried updating this in server.xml, but it doenst seem to help. Could there be somewhere else we need to update?

[lbeuster]

Hi, same for us. Reverse-proxy config looks good.

The people having the most trouble use Chromium on Ubuntu and get a 403 http error in the background.

[ABHISHEK]

Hello Kevin Deuel

Can you elaborate your problem ? so may me be or some one else try to figure out that solution or else have you try to put below line in conf/context.xml ?

<Context sessionCookieName="CONFLUENCESESSIONID">

[Kevin Deuel]

Hey All,

Sorry for the super late reply back. We were using a NetScaler proxy for accessing Confluence. We found that WebSockets were not enabled. Once we enabled WebSockets, it worked for us.

We did eventaully, though, have to turn off Collaborative Editing because it was at times very very slow to update and in some cases would never update :(
Great feature, but seems just too bugy for our systems.

Thanks!
-Kevin

[ramarao chetlapalli]

I started getting this error after I upgraded to latest 6.1.3 server. It is most frustrating for many users

[Dave Nurney]

I have had no reply but I turned off Collaborative editing which seems to have cleared it in the main.

[RyanM]

I've just upgraded from 5.9.3 to 6.1.3 and am also seeing this exact issue. Interesting, I'll keep searching for reports and solutions