Non-zero exit code: 128 Error executing command: Unable to find remote helper for http

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When testing a new Git Repository the following ERROR occurs:

1 2 3 4 5 6 7 8 9 10 11 12 13 Testing Connection Exception executing command "/export/home/apps/fisheye/bin/git ls-remote -h http://<USERNAME>:<PASSWORD>@<GIT_HOST>/scm-manager/git/test " Non-zero exit code: 128 com.atlassian.utils.process.ProcessException: Non-zero exit code: 128 Error executing command "/export/home/apps/fisheye/bin/git ls-remote -h http://<USERNAME>:<PASSWORD>@<GIT_HOST>/scm-manager/git/test ": fatal: Unable to find remote helper for 'http' Error testing connection. Error talking to repository: fatal: Unable to find remote helper for 'http' Connection failed.

Cause

This ERROR is caused when you have an Environment Variable called GIT_EXEC_PATH.

Resolution

Remove the GIT_EXEC_PATH variable from the User running FishEye/Crucible and add it manually to the Settings:

  1. Go to Administration

  2. Click on Global Settings > Server

  3. Now set the path to the Git Executable

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.