Jira uses different URLs to render Confluence links

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Problem

When viewing a Jira issue that is linked with one or more Confluence pages, the following problems may happen:

  1. The Confluence icons are broken

  2. The links of the pages in Issue Links section are incorrect and display a blank page/404 Not Found upon being clicked

  3. If the issue is in a Service Management project integrated with Confluence Knowledge Base, the links of the suggested KBs are incorrect and display a blank page/404 Not Found too

    (Auto-migrated image: description temporarily unavailable)
    (Auto-migrated image: description temporarily unavailable)

Cause

Jira uses different URLs to render Confluence links:

  • The Display URL of the Confluence applinks is used to render Confluence icons and related KB articles

  • The Base URL of Confluence is used to render the linked pages in Issue Links section (mentioned in and Wiki Page)

⚠️ If the above URLs are not configured properly e.g. pointing to a non-existent/inaccessible URL, the problems happen.

Resolution

Double check and ensure that:

  1. Confluence's Base URL is set correctly

  2. The Display URL of the Confluence applinks in Jira is set correctly, and it should be the same as Confluence's Base URL

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.