JIRA 6.2: JIRA is having difficulty contacting fisheye. If this condition persists, please contact your JIRA administrators

[Neal Culiner]

I'm getting the message: JIRA is having difficulty contacting fisheye. If this condition persists, please contact your JIRA administrators within issues. Fisheye is working fine and the application link is set, the dashboard shows fisheye changes, etc. all fine. I don't know how to resolve this issue within issues, right side, development section.

[Piotr Swiecicki · Accepted solution]

The development panel introduced in Jira 6.2 requires App Links with OAuth and 2-legged authentication enabled. See https://confluence.atlassian.com/display/JIRA/Streamlining+your+development+with+JIRA#StreamliningyourdevelopmentwithJIRA-Applicationlinksand https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Code+Development+Tools#IntegratingJIRAwithCodeDevelopmentTools-ConnectingStash,FishEye/CrucibleorBambootoJIRABoth document explain how to enable such authentication method.

Hope that helps,
Piotr

[Neal Culiner]

I've had problems with OAUTH as I don't use SSL and I don't use port numbers with custom tomcat configs. I'll give it another try and see. It's a shame other than oauth methods are not supported.

[Neal Culiner]

Enabling OAUTH worked, thanks.

[Neal Culiner]

It would have probably helped and saved me time, you time, and other's time if JIRA detected OAUTH was disabled and not even shown the developer section OR posted a message that OAUTH is required for this feature.

[annu tewari]

Hello,

I have enabled OAUTH both in JIRA and FISHEYE. Even then am getting the same message.

Please help with the problem and solution for this.

Regards,

Annu

[Luther Hargrove]

Could you have certificates that are outdated? This will be especially important if your sites run over SSL and you have a certificate that has not been updated.

[Neal Culiner]

We don't use SSL or OAUTH. JIRA is communicating to Fisheye find elsewhere, just not in the issue page.

[Jeff Miller]

We don't use SSL, but do use OATH (with 2LO enabled). In Stash, I can see the JIRA issues linked to commits. I can click on them and bring them up. From the other direction, however... in JIRA, the development panel on my issue shows the "JIRA is having difficulty contacting Stash." AAARRRGGGG!

[James Sweeney]

I'm having the same issue with JIRA & Stash, using Trusted Applications, not OAuth. We are running over SSL, but that wasn't an issue prior to the upgrade