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

Crucible - integration with GitHub using ssh keys.


I'm trying to establish secure connection between Crucible (standalone instance) and GitHub repository using ssh key. When repository was configured to use https connection all was working just fine, but when I switch git authentication to ssh key, test of the connectivity returns error:

Error testing connection.
Error talking to repository: 

Permission denied (publickey). 
fatal: The remote end hung up unexpectedly

at com.atlassian.fisheye.git.GitScmConfig.testConnection(
at com.cenqua.fisheye.RepositoryConfig.testConnection(
at com.atlassian.fisheye.spi.admin.impl.DefaultRepositoryAdminService.testConnectionFor(
at sun.reflect.GeneratedMethodAccessor8112.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
Connection failed.

Steps that was made:

  1. Existing repository was chosen (test_repo).
  2. In tab SCM Details:
    1. Repository location changed from ''
      to 'ssh://'.

    2. Git authentication style changed from 'Password for http(s)' to 'Generate key par for ssh'.
    3. Ssh keys was generated.
    4. Public key was copied in to Personal settings -> SSH keys on GitHub account.
    5. Checkout URL was changed from 'https://username/' to 'ssh://'
    6. Connections was tested.

As I mentioned earlier, test connection returns error. My question is this type authorizations is possible, and if it is, is there any description or guide how to do that? Where private key that was generated by Crucible are stored? Ho I can test manually connectivity?


2 answers

1 accepted

1 vote
Answer accepted
lpater Atlassian Team May 04, 2015

Hi Marcin,

this should work as you'd expect.

Please verify the url for the repository is the correct one, exactly as visible on the github page.

Github ssh repository urls have the format of '' - note no 'ssh://' prefix nor username present in the url.

If the url is correct, you could also do a check using

ssh -T -i path-to-private-key

The keyfile fisheye uses for a given repository is stored in FISHEYE_INST/data/auth/repositoryname. This command should result in something like:

Hi username! You've successfully authenticated, but GitHub does not provide shell access.

if the key is recoginzed, and:

Permission denied (publickey).


Hi @Lukasz Pater,

Firstly, I want to thank you for a help, your advice was 100% accurate. 
To setup this connection I was using documentation from this link:
In the paragraph called 'Generate key pair for SSH' there is example of the repository location: ssh:// This is little a bit confusing because I was thinking that ssh:// prefix is mandatory.
I have suggestion to add in to mentioned documentation some example of GitHub repository configuration with repository location in format that you wrote.
Thanks again!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

186 views 1 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you