Confluence displays the warning "Application 'xxx' seems to be offline. Click here to relocate" for application links to Jira when the dark feature "public.access.disabled" is enabled in Jira 10.3.x

XMLWordPrintable

    • 9.12
    • 25
    • Severity 2 - Major
    • 168
    • Hide
      Atlassian Update – 25 August 2026

      Dear Customers,

      This issue is fixed in product releases that include Application Links 10.2.3 or later, or 11.0.4 or later.

      When public access is disabled in Jira, an application that connects to that Jira instance can incorrectly report the application link as offline. The warning can appear even when the application link is configured correctly and authenticated requests continue to work.

      The fix updates the Application Links health check so that it handles the expected response from a Jira instance with public access disabled.

      To resolve the issue, upgrade the application that connects to the Jira instance with public access disabled. This is normally the application that displays the “Application seems to be offline” warning. Upgrading only the Jira instance with public access disabled does not resolve the warning.

      Use the Application Links version matrix to identify the Jira, Confluence, Bitbucket, or Bamboo release that includes the required Application Links version (10.2.3+ or 11.0.4+).

      Best regards,
      Daniel Rauf
      Software Engineer at Jira DC

      Show
      Atlassian Update – 25 August 2026 Dear Customers, This issue is fixed in product releases that include Application Links 10.2.3 or later, or 11.0.4 or later. When public access is disabled in Jira, an application that connects to that Jira instance can incorrectly report the application link as offline. The warning can appear even when the application link is configured correctly and authenticated requests continue to work. The fix updates the Application Links health check so that it handles the expected response from a Jira instance with public access disabled. To resolve the issue, upgrade the application that connects to the Jira instance with public access disabled. This is normally the application that displays the “Application seems to be offline” warning. Upgrading only the Jira instance with public access disabled does not resolve the warning. Use the Application Links version matrix to identify the Jira, Confluence, Bitbucket, or Bamboo release that includes the required Application Links version (10.2.3+ or 11.0.4+). Best regards, Daniel Rauf Software Engineer at Jira DC

      Issue Summary

      When the "public.access.disabled" feature is enabled in Jira 10.3.x, Confluence shows the warning "Application 'xxx' seems to be offline. Click here to relocate" for application links to Jira. Notably, Jira does not display any warnings for links to Confluence, and this message does not impact any functionality.

      Steps to Reproduce

      1. Install Jira Data Center version 10.3.5.
      2. Install Confluence Data Center version 9.3.5.
      3. Create an application link from Jira to Confluence.
      4. Verify that the application link status is "Success" in both Jira and Confluence.  
      5. In Jira, enable the "public.access.disabled" dark feature by
        1. Navigating to [Jira_Base-URL]/secure/SiteDarkFeatures!default.jspa 
        2. In the Enable Dark Feature text field add public.access.disabled
      6. In Jira, go to ⚙ -> Applications -> Application Links. The status for the Confluence link shows as "Connected" with no warnings.
      7. In Confluence, go to ⚙ -> General Configuration -> Application Links. The status for the Jira link shows as "Connected," but a warning message appears: "Application 'Jira' seems to be offline. Click here to relocate."

      Expected Results

      In Confluence, the application link status should be displayed as "Connected" with no warnings.

      Actual Results


      In Confluence, while the application link status shows as "Connected," a warning message appears: "Application 'Jira' seems to be offline. Click here to relocate."

      Workaround

      Disabling the dark feature "public.access.disabled" resolves the warning message.

        1. Screenshot 2025-05-08 at 1.23.10 PM-1.png
          Screenshot 2025-05-08 at 1.23.10 PM-1.png
          237 kB
        2. Screenshot 2025-05-08 at 1.23.10 PM.png
          Screenshot 2025-05-08 at 1.23.10 PM.png
          237 kB
        3. Screenshot 2025-05-08 at 1.22.41 PM.png
          Screenshot 2025-05-08 at 1.22.41 PM.png
          264 kB
        4. Screenshot 2025-05-08 at 1.22.34 PM.png
          Screenshot 2025-05-08 at 1.22.34 PM.png
          270 kB

              Assignee:
              Mateusz Szerszyński (Inactive)
              Reporter:
              Annapoorni
              Votes:
              13 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: