Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crucible / BitBucket issue: fatal: ssh variant 'simple' does not support setting port




Crucible Version:

VersionFishEye 4.5.3 20180321104931 
Crucible 4.5.3 20180321104931

BitBucket Version:

Atlassian Bitbucket v5.11.1

SSH Version:

# ssh -V
OpenSSH_6.6.1p1, OpenSSL 1.0.1e-fips 11 Feb 2013

Git Version: 

# git --version
git version 2.17.1


My crucible install can access the list of repositories in my BitBucket install, but it errors on importing the files, making it so that we cannot open code reviews for anything in our BitBucket.


Is there an easy solution to this issue?




3 answers

1 accepted

0 votes
Answer accepted

I found more error information:

Error testing connection.
Error talking to repository: 

fatal: ssh variant 'simple' does not support setting port

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.
Dick Atlassian Team Aug 07, 2018

Hi Mike,

Thanks for providing these details. I had another look, and it looks like you're running into this bug: FE-7016 (Fisheye stops repository indexing with Git 2.16.0 and higher).

This is caused by a bug in Git 2.16.0+ (

As suggested in the FE-7016 bug, please try one of the workarounds:


  • downgrade Git to version older than 2.16.0 or
  • upgrade OpenSSL to version 6.8 or newer

I hope this resolves your issue.


Thank you!  Updating OpenSSH solved my problem!

Dick Atlassian Team Aug 08, 2018

No worries, Mike! Happy to help.

0 votes
Dick Atlassian Team Aug 06, 2018

Hi Mike,

I did a quick Google search on this error message, and I found:

The internal behavior of Git (>=2.16.0) for SSH tool detection changed and TortoiseGitPlink is not detected any more as ssh or plink compatible.

This only affects if the SSH URL contains a port. For now, you need to set the environment variable GIT_SSH_VARIANT to ssh, in the next version of TortoiseGit 2.5.7 this will be done automatically.


This comment sums it up:

run in git bash git config --global ssh.variant ssh



I hope this helps!

I tried this and it still didn't work.

Dick Atlassian Team Aug 06, 2018

Hi Mike,

I think it's best to raise a ticket with our Support team at Please be sure to link them to this Community thread.

I hope your issue gets resolved soon.


Unfortunately, we're a small team and only need the 5 licences provided by the starter licence, and therefore do not have access to the support system.

This *does* work. You have to make sure that you execute the git config command as the FeCru system user which executes the git commands that fail.

 should mention that I have already re-created the application links. 

Suggest an answer

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

📣 Calling Bitbucket Data Center customers to participate in research

Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...

191 views 2 4
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