add repo on windows 8

Hello, how can I fix the problem (for generated key too) on windows 8:

Error testing connection.
Error talking to repository:

Permissions 0644 for 'key' are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: key
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

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.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(

Connection failed.

2 answers

Hi Sergey,

Do you have cygwin installed on your Windows 8 machine? Basically you have to locate this 'key' file and change it's permissions to one that allows only you to access it.

chmod 0600 /foo/bar/key

The above command should do the trick.

Best regards,

Felipe Alencastro

I have cygwin; I have tried, but it did not help.

And why when I click 'Test connection', seems, fisheye reload key under other generated name? And if I use 'Generate key pair for ssh', how can i define name of generated private key?

Commands continue to return with the exception 'Unable to clone remote repo..':

git clone --bare -v ssh:// clone

git clone --bare -v clone

0 votes
Lukasz Pater Atlassian Team May 19, 2014

Hi Sergey,

What version of FishEye are you using? There was a change in 3.3.1 that might be related -

Before 3.3.1 we tried to set permissions on the key files. As it only worked in some cases, and there is no reliable api to do that on Windows we stopped trying to do that, relying on the administrator to set up the permissions for the FISHEYE_INST directory appropriately.

The error you're getting seems to come from your ssh client expecting the permissions for the keys to be more restrictive. Please check the permissions using cygwins ls command, and make sure they haven't been changed by FishEye if you're using a version before 3.3.1.

You can't define your own key names for generated ssh keys - any reason you would need that?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

61 views 1 5
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you