After updating to Confluence 7.19.4, Unable to connect to websocket.

KubotaDaisuke
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 25, 2023

Updated from 8.13.3 to 7.19.4.
Collaborative editing worked fine in 8.13.3,
but after updating to 7.19.4, I can't connect to websocket and can't create pages.
My configuration is below.

  • AWS ALB > apache > Confluence.
  • Apache 2.4.54
  • Confluence uses context path(/wiki).

 

server.xml has the same settings as in 8.13.3.

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="400" maxPostSize="16777216" minSpareThreads="10" maxParameterCount="5000"
enableLookups="false" acceptCount="10" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol"
scheme="https" secure="true" proxyName="{domain_name}" proxyPort="443"/>

<Engine name="Standalone" defaultHost="localhost">
<Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
<Context path="/wiki" docBase="../confluence" reloadable="false" useHttpOnly="true">
<!-- Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties -->
<Manager pathname=""/>
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/>

<!-- http://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Access_Log_Valve -->
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs"
maxDays="30"
pattern="%t %{X-AUSERNAME}o %I %h %r %s %Dms %b %{Referer}i %{User-Agent}i"
prefix="conf_access_log"
requestAttributesEnabled="true"
rotatable="true"
suffix=".log"
/>

<!-- http://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Remote_IP_Valve -->
<Valve className="org.apache.catalina.valves.RemoteIpValve" />
</Context>

<Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy"
reloadable="false" useHttpOnly="true">
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/>
</Context>

 

No changed any apache settings.

# Synchrony
ProxyRequests Off
ProxyPreserveHost On

ProxyPass /synchrony http://{IP Address}:{synchrony port}/synchrony retry=1 acquire=3000 timeout=600
ProxyPassReverse /synchrony http://{IP Address}:{synchrony port}/synchrony

<Location /synchrony>
RewriteEngine on
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule .* ws://{IP Address}:{synchrony port}/%{REQUEST_URI} [P]
</Location>

# Confluence Server
ProxyPass /wiki http://{IP Address}:{confluence port}/wiki retry=1 acquire=3000 timeout=600
ProxyPassReverse /wiki http://{IP Address}:{confluence port}/wiki

I reconfirmed the apache settings with to the following reference, but I felt that there was no problem.
https://confluence.atlassian.com/doc/using-apache-with-mod_proxy-173669.html

Please let me know if you have any advice on settings that work properly.

Regards,

2 answers

0 votes
KubotaDaisuke
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 25, 2023

I'm sorry. It's a typo.
Update from 7.4.11 to 7.19.4.

0 votes
Mirek
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 25, 2023

Hi @KubotaDaisuke ,

Just to make sure.. since it is hard to imagine how actually you can upgrade Confluence from a version that actually does not exist yet (8.13.3). Is this a mistake and you have in mind 7.13.3?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.19.4
TAGS
AUG Leaders

Atlassian Community Events