Confluence upgrade from v7.0.2 to v7.11.2 broken web access

[Eric Kochis]

I attempted to upgrade Confluence to v7.11.2 with no success.

The upgrade responded successful, the service starts but the web page does not come up.  and Jira shows a "network error" when trying to attach to Confluence.  I believe it is related to the Server.XML file but everything I have tried does not work.  I moved all the settings from the old server.xml over to the new file and it looks correct but the website does not display.  Help!

[Kurt Klinner]

@Eric Kochis 

Can you share the server.xml config, just to double check?

[Eric Kochis]

This is the new merged server.xml file without showing the pw.

<Server port="8000" shutdown="SHUTDOWN" debug="0">
<Service name="Tomcat-Standalone">
<!--
==============================================================================================================
DEFAULT - Direct connector with no proxy, for unproxied HTTP access to Confluence.

If using a http/https proxy, comment out this 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"/>

<!--
==============================================================================================================
HTTP - Proxying Confluence via Apache or Nginx over HTTP

If you're proxying traffic to Confluence over HTTP, uncomment the connector below and comment out the others.
Make sure you provide the right information for proxyName and proxyPort.

For more information see:
Apache - https://confluence.atlassian.com/x/4xQLM
nginx - https://confluence.atlassian.com/x/TgSvEg

==============================================================================================================
-->

<!--
<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"
scheme="http" proxyName="<subdomain>.<domain>.com" proxyPort="80"/>
-->

<!--
==============================================================================================================
HTTPS - Direct connector with no proxy, for unproxied HTTPS access to Confluence.

For more info see https://confluence.atlassian.com/x/s3UC
==============================================================================================================
-->

<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
protocol="org.apache.coyote.http11.Http11Nio2Protocol"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLSv1.2" sslEnabledProtocols="TLSv1.2" SSLEnabled="true"
URIEncoding="UTF-8" keystorePass="XXXXXXXXXXXX"
keystoreFile="C:\Users\confuser\Documents\confluence.jks"/>

<!--
==============================================================================================================
HTTPS - Proxying Confluence via Apache or Nginx over HTTPS

If you're proxying traffic to Confluence over HTTPS, uncomment the connector below and comment out the others.
Make sure you provide the right information for proxyName and proxyPort.

For more information see:
Apache - https://confluence.atlassian.com/x/PTT3MQ
nginx - https://confluence.atlassian.com/x/cNIvMw
==============================================================================================================
-->

<!--
<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"
scheme="https" secure="true" proxyName="<subdomain>.<domain>.com" proxyPort="443"/>
-->

<Engine name="Standalone" defaultHost="localhost" debug="0">
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
<Context path="" docBase="../confluence" debug="0" 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" debug="0"
reloadable="false" useHttpOnly="true">
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60"/>
</Context>
</Host>
</Engine>
</Service>
</Server>

[Eric Kochis]

Hi Kurt- any red flags on the server.xml file?

Thank you!

[Kurt Klinner]

@Eric Kochis 

Hi Eric

sorry for the late reply. The server.xml looks ok so far. I assume that you try to access confluence via https://HOSTNAME:8443 right?

Cheers

Kurt

[Eric Kochis]

Hi Kurt- YES I am attempting to connect to after the upgrade just like I did before the upgrade attempt. (https://kb.oacsd.org:8443)

Thank you,

-Eric

[Kurt Klinner]

@Eric Kochis 

As mentioned the server.xml looks good, so without any additional errors from the catalina.out or application log file i do not have a clue what is causing the issue.

Can you test the upgrade on a lower tier environment?

Cheers

Kurt

[Eric Kochis]

Meaning do an upgrade to a version older than 7.11.2?

IF so, what version do you recommend?

Thanks again,

-Eric 

[Kurt Klinner]

@Eric Kochis 

Depends a bit on your requirements, if you would like to have ensured backports for security topics than you would go with the LTS versions (7.4) at the moment, 7.13 to be released sometimes soon.

Regardless of the version i meant doing a test of the upgrade on a lower tier environment to see if we still hit a problem

Cheers

Kurt

[Kurt Klinner]

@Eric Kochis 

Hi Eric

welcome to the Community.

Did you check the log file for an exceptions / warnings?

Cheers

Kurt

[Eric Kochis]

No I did not.

Yes- all looked good except there was a warning about using two connections, one on port 8443 and one on 8090.  I am using https access on 8443 only and not going through a proxy.

Cheers.

[Eric Kochis]

Yes I did look at the logs :-)

[Eric Kochis]

I only moved over my connection info into the new Server.xml file and made sure to keep the proxy connection remarked....  still no go.