Problem communicating with Stash when adding repository

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

When adding a repository to Fisheye/Crucible using the Stash repositories tab, the following error appears which prevents the page from loading:

Problem communicating with Stash

Did not receive SSH clone URL information from Stash instance. This could be because SSH is disabled or because the Stash version is too old. Atlassian Stash 2.11.4 or later is required.

The following appears in the atlassian-fisheye-YYYY-MM-DD.log

2015-09-17 00:06:27,440 DEBUG [qtp1984513847-586 ] fisheye ProfilingServletFilter-logRequest - start request GET /fecru/rest/stash-integration-plugin/1.0/8c938ee7-cbb5-372e-a9f2-4f0fd28958d9/repos?start=0&limit=500&_=1442448387296 sessionid=msggw8n5jumj991v58dozk6o
2015-09-17 00:06:27,850 DEBUG [Resource Monitor ] fisheye SystemResourceMonitor$MonitoringTask-run - tc=161, ofd=497, mfd=4096, fm=179690792, tm=631238656
2015-09-17 00:06:27,911 WARN  [qtp1984513847-586 ] fisheye StashExceptionMapper-handleException - Error occurred making request to Stash com.atlassian.fecru.plugins.stash.rest.errors.StashTooOldException: Did not receive SSH clone URL information from Stash instance.  This could be because SSH is disabled or because the Stash version is too old.  Atlassian Stash 2.11.4 or later is required.
        at com.atlassian.fecru.plugins.stash.rest.RestStashRepoListService.getStashRepoList(RestStashRepoListService.java:125)
...
2015-09-17 00:06:27,912 DEBUG [qtp1984513847-586 ] fisheye ProfilingServletFilter-logRequest - end request in 473ms GET /fecru/rest/stash-integration-plugin/1.0/8c938ee7-cbb5-372e-a9f2-4f0fd28958d9/repos?start=0&limit=500&_=1442448387296 sessionid=msggw8n5jumj991v58dozk6o 400

Cause

This message can have multiple causes. 

The integration requires that you're running Stash 2.11.4+. Older versions of Stash do not support this integration.

If you're running Bitbucket Server 4.0+ this is caused by a change in the REST API to not return an SSH clone URL if your account is not setup with an SSH key. This change was tracked at  STASH-7827 - Getting issue details... STATUS .

Workaround

If you're running Bitbucket Server 4.0.0 add an SSH key to your profile in Bitbucket Server - SSH user keys for personal use

Resolution

If you're running an older version of Stash before 2.11.4, upgrade to a newer version.

If you're running Bitbucket Server 4.0.0, upgrade to version 4.0.1 where this issue was fixed.

 

Last modified on Jul 31, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.