Solution - Downgrade my Visual Studio Version to 1.64 from 1.66 and successfully deployed.
Angular code deployment to Azure failed - Reason - .azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20Code failed, reason: read ECONNRESET
I am trying to deploy my code from Visual Studio Code (1.66.0) to Azure WebAPP.
Code is getting Build successfully but when I am trying to deploy getting below error.
Error: request to https://igim-admin.scm.azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20 Code failed, reason: read ECONNRESET
If someone face the same issue then please help me out.
Facing the same issue, it works fine if you are using Functions CLI.
just go to the root directory and do this
func azure functionapp publish <APP_NAME>
Sign in to comment
Sort by: Most helpful
BhuwanMittal-0748, Firstly, apologies for the delayed response from over the weekend.
Glad to know that the issue is resolved. Thanks for sharing the solution that worked for you with the community. It's much appreciated.
I'm having the same problem, so you have a solution downgrading, i'm using this link to get your mentioned version:
testinggg....and.... yes, it works.
I hope Microsoft gives a working version soon to be up-to-date again.
I received the a similar error in VS Code. Downgrading from 1.66 to 1.64, I am now able to deploy a Node.js app. Thank you for the information.
first time using azure. downgrading solved the issue
Sign in to comment
I understand the inconvenience with this issue. Apologies for any trouble!
It’s being tracked on VS repo, as mentioned –“until a fix is released in VS Code stable (hopefully the next major release)”.
4 -options are outlined for the fix (downgrading VS code version, is one of the option).
(copied the suggested options below to benefit the community)
- Wait for the fix to come in VS Code Insiders
- Deploy via Azure CLI
- Downgrade your Azure Functions extension version to 1.2.1 (Feb 08, 2021), we used a different zip deploy method which seems to be working still. Note: it might not work in environments like WSL or Codespaces, which is why we changed our deploy in 1.3.0 (Mar 15, 2021).
- Downgrade to the VS Code February 2022 release, where zip deploy is working as discussed and confirmed above.
Thanks for your patience!