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

after upgrade, fisheye cannot authenticate to jira

We upgraded Jira to version 5.2.9 and Fisheye from version 2.7.x to 2.10.4. However when we went to use jira for user management, we get a the error below. This despite the fact that we went to the Jira user server in Jira and added the application name and created a password, both of which we use when we try to set up Jira user management on the Fisheye side.

"Problem communicating with JIRA: Connection refused"

6 answers

0 votes
Foong Atlassian Team May 15, 2013

Are you using JIRA DNS or IP address when connecting from FishEye server? Please try using localhost at FishEye Authentication setting to connect to JIRA and make sure that is added into JIRA User Server.

I'm having the exact same issue. This is a first-time install of Fisheye/Crucible, and we're trying to use our existing Jira user database. Putting in the correct details gives the exact error above - but the authentication details are then saved. Users aren't collected though, so there's nothing in the 'users' screen.

Also, clicking 're-sync' gives an alert "Error synchronising users: Problem communicating with Crowd", and clicking 'edit' shows: "Your request was unable to be processed java.lang.ArrayIndexOutOfBoundsException - -1"

0 votes

In the JIRA User Server, what IP address have you added? localhost and the IPv4 AND IPv6 representation of localhost? Check if you have IPv6 enabled on the server and if this is an issue. By default I've seen JIRA miss this when establishing the user management / application link.

On the Jira User Server I have tried adding the ip address of the nic we've assigned to fisheye and to whom the proper dns record points to. (Although we've put Jira and Fisheye on the same server, traffic for each comes in via separate ip's.) I've also tried with though not the IPv6 version of localhost. We have IPv6 disabled via /etc/sysconfig/network (CentOS). The strange thing is that we are also using stash, also on the same box and had no problem using Jira as the user server there.

The application links from Fisheye to Jira seem to be working fine. Jira is a trusted application and is set to provide incoming and outgoing OAuth access. I had no issues setting that up. Is there anything else to test issues from Fisheye to Jira?

The issue seems to be in the network connectivity as you are getting a connect exception. See if you can ping the JIRA box from your Fisheye box. Maybe your firewall is blocking requests from Fisheye on JIRA as well.

Its possible but I was able to create full trust application links between the two applications. In fact, when I go to the "Fisheye Configuration" screen in Jira, I see that there is communication between the two as both the Crucible Project list cache and the Repository List cache were refreshed as of a few hours ago.

Also, These applications are on the same box. Although traffic for each goes comes in from the outside via two different ip addresses (and nics) they do reside on the same machine.

That is from JIRA to Fisheye. Is the application link also working from Fisheye to JIRA? Looks like there is probably an issue only from Fisheye server to JIRA

Also notice that sometimes we get the following error:

Problem communicating with JIRA: <!DOCTYPE html> <html> <head> <title>Forbidden (403)</title> <!--[if IE]><![endif]--> <script type="text/javascript">var contextPath = '';</script> <link type="text/css" rel="stylesheet" href="" media="all"> <!--[if lte IE 8]> <link type="text/css" rel="stylesheet" href="" media="all"> <![endif]--> <!--[if lte IE 9]> <link type="text/css" rel="stylesheet" href="" media="all"> <![endif]--> <!--[if IE 9]> <link type="text/css" rel="stylesheet" href="" media="all"> <![endif]--> <link type="text/css" rel="stylesheet" href="" media="all"> <link type="text/css" rel="stylesheet" href="

Can't put the entire error as the comment field here does not allow more than 2000 charachters.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events