How fix Azure web app deploy error with VSCode?

Question

I followed quickstart-nodejs guide. Difference is region. guide region is 'eu', my region is 'kor'.

https://learn.microsoft.com/ko-kr/azure/app-service/quickstart-nodejs?tabs=windows&pivots=development-environment-vscode

Error came when after zipping.

오후 3:46:22: Error: request to https://mpexpressapp011.scm.azurewebsites.net/api/zipdeploy?isAsync=true&author=VS%20Code failed, reason: read ECONNRESET

Why and How?

Please help me. (ㅠㅠ)

What is the region you have selected Korea Central or Korea South ? — Harshitha Veeramalla
– Harshitha Veeramalla, Commented Mar 31, 2022 at 9:00
I have followed the document and able to deploy the application and able to acces the application successfully. Could you please share the screen shot of the error — Harshitha Veeramalla
– Harshitha Veeramalla, Commented Mar 31, 2022 at 9:16
I solved it by downgrading the VSCode version. (1.66 -> 1.64.2) Thank you everyone! We are the world! — NedCrow
– NedCrow, Commented Apr 1, 2022 at 1:42
You can get the older versions from this link code.visualstudio.com/updates/v1_65 — Pushpanathan K
– Pushpanathan K, Commented Apr 4, 2022 at 15:13

DeveloperAlwaysTired · Accepted Answer · 2022-03-31 14:38:22Z

15

Exactly the same issue since yesterday, Brazil South region. Stopped working out of the blue.

EDIT: After rolling back Visual Studio Code update to february, it works again. Looks like the update from VScode broke something

edited Mar 31, 2022 at 14:38

answered Mar 31, 2022 at 14:29

DeveloperAlwaysTired

1761 silver badge5 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Shawn McGough Over a year ago

Rolling back to February (version 1.65.2) fixed it.

Shawn McGough Over a year ago

Issue reported here: github.com/microsoft/vscode/issues/146470

Alberto Sanches · Accepted Answer · 2022-03-31 15:21:14Z

3

After rolling back Visual Studio Code update to february, it works again. Looks like the update from VScode broke something.

Aye!!! It worked here too!

answered Mar 31, 2022 at 15:21

Alberto Sanches

311 bronze badge

Comments

Carlos Eduardo Gonalves Junior · Accepted Answer · 2022-04-01 14:14:10Z

2

I have experienced that same problem, but I follow the Alberto Recommendation and worked perfectly here, I did downgrade from 1.66 to 1.65.2.

answered Apr 1, 2022 at 14:14

Carlos Eduardo Gonalves Junior

211 bronze badge

2 Comments

farshad Over a year ago

Providing more info on the procedure and a link could help the OP solve the issue faster.

Dumber_Texan2 Over a year ago

Same issue. Running 1.66.0. It worked last week. According to Windows 10, 1.66.0 was installed on 3/30/22. Has anyone filed a bug?

Phil Catterall · Accepted Answer · 2022-04-01 11:25:54Z

1

Same issue for me too, deploying in UK SOuth. Rolled back to January (1.64.2 to be safe) and worked perfecty. So I would agree, some new issue in the March release (1.66.0)

answered Apr 1, 2022 at 11:25

Phil Catterall

575 bronze badges

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Shizu · Accepted Answer · 2022-04-03 08:21:53Z

1

The situation was the same in Japan. After hours of trying various things, I was able to find and solve it. I don't know who put it in, but the crime of taking a lot of time from developers around the world is very heavy.

answered Apr 3, 2022 at 8:21

Shizu

111 bronze badge

1 Comment

Ankur Lahiry Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Nik Holden · Accepted Answer · 2022-04-09 22:44:32Z

1

Same in NZ. New laptop upgrade to V1.66 and would not work. Uninstalled and installed V1.65 and the upload worked. Interestinglky the size of the sipped filed was 1Mb smalled with the 1.66 version (1.66 size of zipped file was 58.3 Mb and 1.65 and below size of zipped file is 59.4 Mb)

answered Apr 9, 2022 at 22:44

Nik Holden

212 bronze badges

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Santhosh s · Accepted Answer · 2022-04-10 11:32:56Z

1

Yes, I also encountered the same issue in INDIA. downgrading the application to Jan Version: 1.64.2 (Universal) resolved the issue.

I am using a Macbook air (M1 chip)

You can download other versions from here

answered Apr 10, 2022 at 11:32

Santhosh s

1941 silver badge5 bronze badges

Comments

Igor Ferreira · Accepted Answer · 2022-04-11 16:34:51Z

1

It worked after reverting to previous version

answered Apr 11, 2022 at 16:34

Igor Ferreira

111 bronze badge

Collectives™ on Stack Overflow

How fix Azure web app deploy error with VSCode?

8 Answers 8

2 Comments

Comments

2 Comments

1 Comment

1 Comment

1 Comment

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

2 Comments

Comments

2 Comments

1 Comment

1 Comment

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related