An error occurred when trying to create the application link in the remote application (Link Confluence to JIRA)

[sandro gehrig]

Hi all

We got development instances for both of our atlassian systems, confluence and jira.

While trying to create the application link from dev.confluence to dev.jira I get this error message at step 3 "Set Users and Trust". It does not matter whether I tik the options "Same set of users" and "full trust each other"(which I need) or any other combination.

Error Message:

An error occurred when trying to create the application link in the remote application.
Cannot update the remote applications URL. Please use the link relocation functionality instead.

The server logs nothing while this error appears.

Any ideas?

Regards

sandro

[Thomas Wendel · Accepted solution]

Hi Sandro,

Please try the following:

• Try to establish the application link from the other application, form dev.jira to dev.confluence (I know this sounds silly, but give it a try)
• Does the user, with which you are trying to establish the application link have admin permissions on the remote application?
• Are the applications base URLs the same as the ones you used to create the link? E.g. if your Confluence base URL is http://dev.confluence resp. http://dev.jira for JIRA, do you use those URLs to establish the application link? You will most likely get problems if you are using IP-addresses or localhost here. You must be able to reach the other application with it's base URL! As a workaround you can use an entry in the hosts file on the servers to make sure your domain names get resolved properly.
• If you are using SSL certificates for one or both of your applications make sure that the certificates are in the keystore of the remote application. Please refer to https://answers.atlassian.com/questions/30519/create-application-link-between-jira-and-confluence-problem-with-different-userbase-or-with-ssl</li<>>
• Please let me know if you got it working.

Cheers,
Thomas

[sandro gehrig]

Thanks thomas, doing it from the other site (your first guess) did the trick. Wonder why I didn't think about that on my own.

Btw: The server DID log something, something like this

WARN [http-8090-1] [atlassian.applinks.ui.BatchedJSONi18NBuilderFactory] put Duplicate i18n entry for key 'applinks.auth.provider.com.atlassian.applinks.api.auth.types.OAuthAuthenticationProvider'

Guess it had something to do with the link i deleted previously. The instance in fact is a copy of the production, but with dev license applied. The DB still had some orphaned entrys I think.

however, thanks and happy easter weekend!

sandro