Issue links fail to display with Page Failed to Load error in Jira server

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

Environment

Jira 6.0.4 and later, 7.x, 8.x, 9.x, 10.x

Problem

Symptoms

On a given issue, the Issue Links section show "Page Failed to Load" for links to Confluence.

(Auto-migrated image: description temporarily unavailable)

The following appears in the atlassian-jira.log:

First stack trace

1 2 3 4 2014-11-08 22:42:58,490 http-bio-8080-exec-850 ERROR superman 1362x118732x1 5w5742 x.x.x.x,0:0:0:0:0:0:0:1 /rest/viewIssue/1/remoteIssueLink/render/10230 [viewissue.issuelink.rest.RemoteIssueLinkResource] Error occurred while generating final HTML for remote issue link: java.lang.RuntimeException: java.io.IOException: Failed to load Confluence Page from remote server Caused by: java.io.IOException: Failed to load Confluence Page from remote server Caused by: com.atlassian.sal.api.net.ResponseException: Confluence remote API is disabled

or

Second stack trace

1 2 3 4 5 2014-10-28 14:03:56,368 ajp-bio-8042-exec-11 ERROR batman 843x1796x1 1kn3f8r x.x.x.x /rest/viewIssue/1/remoteIssueLink/render/10502  [viewissue.issuelink.rest.RemoteIssueLinkResource] Error occurred while generating final HTML for remote issue link: java.lang.RuntimeException:  java.io.IOException: Failed to load Confluence Page from remote server Caused by: java.io.IOException: Failed to load Confluence Page from remote server  Caused by: com.atlassian.sal.api.net.ResponseException: Status Code: 200, Status Text: OK, Errors: {}, Error Messages: [java.lang.Exception: RPC handler object "confluence2" not found and no default handler registered]

Cause

The JIRA Remote API plugin fails to connect to Confluence using the XML-RPC and throws an exception.

Resolution

First stack trace: Enable the remote API in Confluence as per this KB article: Enabling the Remote API. There is an open ticket asking JIRA to switch to REST instead of XML-RPC for page retrieval: JRASERVER-61128 - JIRA should use REST API to search Confluence pages and Link Jira Issues

Second stack trace: Enable the Confluence Remote API system plugin via Manage Add-ons > System.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.