This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 62%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH%3C/text%3E%3C/svg%3E)
I am running an Azure WebApp with Node 14 LTS and its connected to my private GitHub repository. My deployments were running on each code commit automatically until October and now I tried to deploy new code again and only end up with this error:
error: cannot run ssh: No such file or directory
fatal: unable to fork
/usr/bin/git fetch origin --progress
I only modified my code, pushed to the repository and expected the deployment to run - which obviously does no longer work. I found several such posts on the Internet but not how to solve it.
Any thoughts?
Harry.
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
Answer accepted by question author
@Harry , we are sorry for the error that you encountered.
Can you please try adding SCM_ENABLE_DYNAMIC_INSTALL=false as an app setting to your app? Please note that this will cause a reboot to your app.
After several redeploy/sync tries it started working again!
Thanks for your help!
I wonder why this broke in the first place - thats not what I expect from an App service. :-/
Harry.
@Harry There was an update that went out towards the end of October that broke how the SSH keys were handled. While the team quickly identified the cause and a fix, non critical platform updates are not allowed for most of November to ensure stability for the holidays. This meant the fix did not start being deployed until early December and just finished being applied to the final data center a few data ago.
This issue, while frustrating, was deemed as non-critical as the app setting mentioned in yesterday's reply was found to be a workaround.
We do apologize for the frustration that you encountered and thank you for your business.
Happy New Year!
One more detail: After I pushed the first change to the repository, I got this error message. After that, with further code changes, nothing happens anymore.
Harry.