Cannot edit articles

Hi,

i installed a new confluence installation, which is accessed with http.

I can create articles, but not edit. When i start edit an article, i get the following error message:

16-Aug-2017 08:28:39.979 SEVERE [http-nio-8090-exec-4] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null

 

I am using CentOS 7, my confluence version s 6.2.1

 

How can i resolve my problem?

Thanks!

2 answers

0 vote

Hi Thomas,

Can you let me know, does it occur for all users and on multiple browsers, and multiple workstations? Is the user logged out after this error occurs?

I have another user that was able to resolve the issue by changing the directives in vhosts container following this article:

Using Apache with Mod Proxy

So you may want to take a look at this and see if it matches your situation.

Kind Regards,
Shannon

Hi,

 

thanks for the answer.

I already tried multiple browsers and users.

I created a new user, created a new site and published. After i start editing and click "save", i get the same error again.

The user is not logged out after the error occurs.

The problem occurs also, if i access confluence directly by access port :8090.

server.xml Connector:

        <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="docs.corp.domain.at" proxyPort="80" scheme="http" />

 
And my apache vhost:

<VirtualHost *:80>
    ServerName docs.corp.domain.at
     
    ProxyRequests Off
    ProxyVia Off
     
    <Proxy *>
         Require all granted
    </Proxy>
 
    ProxyPass / http://localhost:8090/
    ProxyPassReverse / http://localhost:8090/
</VirtualHost>

 

Can you help me?

0 vote
Ann Worley Atlassian Team Aug 21, 2017

@Thomas Manninger Please see the example under the heading, "If you're using Confluence 6.0 or later with Synchrony" on this page:

Proxying Atlassian server applications with Apache HTTP Server (mod_proxy_http)

You need an entry for Synchrony (collaborative editing) in your proxy configuration.

The server.xml is (correctly) set up to direct requests on port 8090 back through the proxy, that's probably why the issue still presents itself when you access the instance directly on that port.

I wanted to share some other general information on Collaborative Editing:

Troubleshooting Collaborative Editing

Please check out the network diagrams on:

Administering Collaborative Editing

Hi,

We have same mesages in logs, but collaborative editing works:

31-Oct-2017 13:21:09.636 SEVERE [http-nio-8082-exec-9] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null
31-Oct-2017 13:24:24.836 SEVERE [http-nio-8082-exec-8] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null
31-Oct-2017 13:24:35.513 SEVERE [http-nio-8082-exec-8] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null
31-Oct-2017 13:24:43.320 SEVERE [http-nio-8082-exec-2] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null
31-Oct-2017 13:26:54.707 SEVERE [http-nio-8082-exec-11] org.springframework.web.socket.server.support.DefaultHandshakeHandler.handleInvalidUpgradeHeader Handshake failed due to invalid Upgrade header: null

 

We use apache mod_proxy (Apache 2.4.x)., Revers proxy configuration:

<VirtualHost *:80>
ServerName wiki.domainname.com
DocumentRoot /var/www/html/wiki
ErrorLog /var/log/httpd/wiki-error_log
CustomLog /var/log/httpd/wiki-access_log combined
HostnameLookups Off
UseCanonicalName Off
ServerSignature off
RemoteIPHeader X-Forwarded-For
ProxyVia On
ProxyPreserveHost On
# RewriteEngine On
ProxyRequests Off

RewriteEngine On
RewriteCond %{REQUEST_URI} !^/synchrony
RewriteRule ^/(.*) http://127.0.0.1:8082/$1 [P]
# Auth changes in 2.4 - see http://httpd.apache.org/docs/2.4/upgrading.html#run-time
<Proxy *>
Require all granted
</Proxy>

ProxyPass /synchrony http://127.0.0.1:8091/synchrony
<Location /synchrony>
Require all granted
RewriteEngine on
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule .* ws://127.0.0.1:8091%{REQUEST_URI} [P]
</Location>

ProxyPass / http://127.0.0.1:8082/
ProxyPassReverse / http://127.0.0.1:8082/

<Location />
Require all granted
</Location>

</VirtualHost>

 

What is wrong in our configuration?

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jul 10, 2018 in Confluence

We want to see the templates you've created in Confluence!

Hi Community, Jessica here from the Confluence Product Marketing team!  July’s community challenge is all about sharing pictures  — and as an extension of our first post on what ...

869 views 23 12
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you