'Page Not Found' error after installing Confluence Data Center in Kubernetes Cluster

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Data Center and Cloud By Request - This article was written for the Atlassian data center platform but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

 

The steps outlined on this article are provided AS-IS. This means we've had reports of them working for some customers — under certain circumstances — yet are not officially supported, nor can we guarantee they'll work for your specific scenario.

You may follow through and validate them on your own non-prod environments prior to production or fall back to supported alternatives if they don't work out.

We also invite you to reach out to our Community for matters that fall beyond Atlassian's scope of support!

Summary


After Installing Confluence using Helm Chart in Kubernetes cluster, when users are trying to access Confluence site the page is displaying 'Page Not Found' error. As shown below

Environment

  • Kubernetes
  • Nginx Ingress Controller
  • Confluence Helm chart (all versions)
  • Supported Database 

Diagnosis

  • Error can be seen in confluence_access.<date>.log

  • Please use below command to grep the line related to the error from the access logs

     grep -i '"GET /confluence HTTP/1.1" 404' confluence_access.<date>.log
  • Below Error can be seen in confluence_access.<date>.log

    xx.xxx.xx.xxx - [<Date>:<Time>] "GET /confluence HTTP/1.1" 404 56326 885 /confluence http-nio-8090-exec-2 "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36

Cause

Absence of contextPath under # Confluence Configuration section in Confluence Helm Chart.

# Confluence configuration
#
confluence: 
...

    # -- The Tomcat context path that Confluence will use. The ATL_TOMCAT_CONTEXTPATH
    # will be set automatically.
    #
    contextPath:


However, Ingress resource have base path defined as /confluence under # Ingress configuration in Confluence Helm Chart

# Ingress configuration
#
# To make the Atlassian product available from outside the K8s cluster an Ingress
# Controller should be pre-provisioned. With this in place the configuration below
# can be used to configure an appropriate Ingress Resource.
# https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#ingress
#
ingress:

...

# -- The base path for the Ingress Resource. For example '/confluence'. Based on a
  # 'ingress.host' value of 'company.k8s.com' this would result in a URL of
  # 'company.k8s.com/confluence'. Default value is 'confluence.service.contextPath'
  path: '/confluence'


Solution

Please perform below steps:

  1. Add contextPath under Confluence configuration section in Confluence helm chart (value.yaml) like below:

    # Confluence configuration
    #
    confluence: 
    ...
    
        # -- The Tomcat context path that Confluence will use. The ATL_TOMCAT_CONTEXTPATH
        # will be set automatically.
        #
        contextPath: /confluence
  2. Uninstall current deployment and delete local-home, shared-home, synchrony PVC (no need to delete if they are empty)

  3. Redeploy confluence application
  4. Access confluence site after clearing the browser cache or check in private browser mode and verify the issue.

In case of further assistance please reach out to the Atlassian Support team and share the information that's been gathered so far along with a fresh Support zip file.


Last modified on Aug 22, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.