FTP-Deploy-Action: The process '/usr/bin/git' failed

This is not a GitHub issue. GitHub happened to be having issues on the same day.

This is the exact same issue as last time. The underlying docker image pushed a breaking update. See root cause description this comment https://github.com/SamKirkland/FTP-Deploy-Action/issues/345#issuecomment-1353339618

I just need to update the underlying docker image to a truly stable and working image. Actively looking for a image that meets the criteria.

I was still having this issue on 3.1.2, but I fixed it by forking the project and running this prior to the upload. (It made no difference if I just ran it in a prior step of the action) I discovered this by adding a git branch step, and it was reporting some issues with the local git repo. I think it has to do with permissions of the directory when running in the debian container.

git config --global --add safe.directory /github/workspace

I have a legacy project that still requires SFTP, so unfortunately I have to do this instead of migrating to 4+.

I was thinking about creating a PR with this fix. My initial though is to just add a param that accept an arbitrary script that’s executed before the git-ftp sync. Let me know your thoughts. Thanks!

Thank you for all your effort on this @SamKirkland !

@ermincelikovic thanks for the quick response! Looks like i need to push an update to the tag (it’s still referencing the old code)

In the meantime can you use the patched version and let me know how it goes? In your action update the version to v3.1.2-patch

It should look something like uses: SamKirkland/FTP-Deploy-Action@v3.1.2-patch

Thank you for the patch @SamKirkland, but unfortunately for me it is not working, now a different error code pops up:

  Thu Feb  2 18:14:03 UTC 2023: The remote sha1 is saved in file '.git-ftp.log'.
  Thu Feb  2 18:14:03 UTC 2023: Check if curl is functional.
  Thu Feb  2 18:14:03 UTC 2023: fatal: Protocol 'sftp' not supported by curl, exiting...
  ::endgroup::
Error: The process '/usr/bin/git' failed with exit code 5

If you need help to test any patch, just let me know.

Sorry guys but those last errors looks different enough and not directly related to the original issue. The original problem has been fixed in 3.1.2-patch and this issue should already have been closed long ago.

It feel like this thread became a mix of different problems, can you please create dedicated issues for those.

Uploading files /usr/bin/git ftp push --force --auto-init --verbose --syncroot=./ --user=*** --passwd=*** --insecure Thu Feb 2 13:08:04 UTC 2023: git-ftp version 1.6.0 running on Linux 8b8f91928bde 5.15.0-1031-azure #38-Ubuntu SMP Mon Jan 9 12:49:59 UTC 2023 x86_64 Linux Thu Feb 2 13:08:04 UTC 2023: Forced mode enabled. Thu Feb 2 13:08:04 UTC 2023: Auto init if needed. Thu Feb 2 13:08:04 UTC 2023: Using syncroot ./ if exists. Thu Feb 2 13:08:04 UTC 2023: Insecure SSL/TLS connection allowed Thu Feb 2 13:08:04 UTC 2023: Syncroot is ‘./’. Thu Feb 2 13:08:05 UTC 2023: User is ‘***’. Thu Feb 2 13:08:05 UTC 2023: Password is set. Thu Feb 2 13:08:05 UTC 2023: CACert is ‘’. Thu Feb 2 13:08:05 UTC 2023: Insecure is ‘1’. Thu Feb 2 13:08:05 UTC 2023: Proxy is ‘’. Thu Feb 2 13:08:05 UTC 2023: The remote sha1 is saved in file ‘.git-ftp.log’. Thu Feb 2 13:08:05 UTC 2023: Check if curl is functional. Thu Feb 2 13:08:05 UTC 2023: fatal: Protocol ‘sftp’ not supported by curl, exiting… Error: The process ‘/usr/bin/git’ failed with exit code 5

@SamKirkland SamKirkland/FTP-Deploy-Action@v3.1.2-patch - works for me.

@SamKirkland Error: Unable to resolve action SamKirkland/FTP-Deploy-Action@3.1.2-patch, unable to find version 3.1.2-patch

You are missing the v

@SamKirkland - still does not work (with v3.1.2-patch) - but seems like it’s due to sftp?

 Thu Feb  2 08:52:18 UTC 2023: The remote sha1 is saved in file '.git-ftp.log'.
 Thu Feb  2 08:52:18 UTC 2023: Check if curl is functional.
 Thu Feb  2 08:52:18 UTC 2023: fatal: Protocol 'sftp' not supported by curl, exiting...

@SamKirkland Still fails (with 3.1.2)