Cannot set Confluence as Trusted Application Because their Host Could not be Found

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

Summary

Symptoms

Trusted Application communication fails. JIRA displays "The host xxxxxx could not be found".

(Auto-migrated image: description temporarily unavailable)

The following appears in the atlassian-jira.log:

1 2 3 4 INFO: Malformed security token atlassian:qj4VF65XgDg7lvE0RRoO307Qa1klmtmIU5931K02z5ICP2wi0askQhUqh+b7uNpmtRKVMfA7P7PD5DRT6+4485ApKK312MsGlSpBpthvHLbBty5lJxqGtGQViMPqRblY97cIs8STRdoRErwDtmAnJ/RN4LuVXBB8N fBAyImvI0+pCZEHm4syoX/5J5XhUVz4M5VJt53DgnlP6sn1T78/reQI2Jm+Or/OplifV22iItYoGco/+P1eMdw/GwOkRUR/21cMr1FBp1wW3l2fcN/p0NCxOqxSCFu5isYyR/ShTRKXnszP8uOxlF7+Cx+MZRfsJEQPNQ== org.apache.shindig.auth.SecurityTokenException: org.apache.shindig.common.crypto.BlobExpiredException: Blob expired, was valid from Fri Jan 21 15:23:16 EST 2011 to Fri Jan 21 16:29:16 EST 2011, attempted use at Mon Jan 24 10:27:09 EST 2011

Diagnosis

Network connection is intact. A ping or traceroute from the host to the destination IP address works.

Cause

JIRA cannot reach Confluence instance because they are working on different protocols (one over HTTP, other SSL).

Solution

Resolution

JIRA and Confluence must use the same communication protocol. So set both applications to use HTTP or SSL.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.