Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Application link "Network error"


I'm having issue in one direction of an application link.

Basically I have set up Jira, Crowd, Crucible in one server A, Confluence in another server B. All self-hosted, and are all proxied by server C.

Jira, Crowd and Confluence have been running for over 6 months. Today I installed Crucible.

Jira is at 8.13.0 (starter licence)

Confluence is at 7.8.1 (starter licence)

Crowd is at 3.4.4 (starter licence)

Crucible is at 4.8.5 (trial licence)


I can access each application individually.

Using Jira as the focal point:

1. Jira can link to Confluence - Status is Connected. I can Go to remote, and in Confluence, Status is also Connected.

2. Jira can link to Crowd - Status is Connected. I can Go to remote, and in Confluence, Status is also Connected.

3. Jira CANNOT link to Crucible - Status will first show Deprecated, then Network Error. But I can Go to remote, and in Crucible, Status is Connected! From Crucible, I can Go to remote! Still "Network error" though.

There is nothing in strange in Jira's catalina.out. No other log files are being written at times of showing this Network error.


One thing I find strange is that in Jira, "FishEye/Crucible integration into Jira" setting under Admin | Applications | Integrations | FishEye will always default back to "Crucible integration only". 


I haven't started using Crucible yet... still trying to get the configuration correct.

I searched inside Crucible after adding a BitBucket repository, and there is seems to be no where that I can create a Jira issue from commits. Is this because the link is broken in the Jira side?


Any idea if this Application link should be fixed, or it doesn't hurt anything? 

1 answer

1 accepted

1 vote
Answer accepted

I found the cause of error.

In Crucible config.xml, context must prefix with a /.


When it doesn't work, I was using :


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events