Azure-docs: The Given instructions does work....

[QiiLin]

I did the above steps....the sample code/instructions does not work..when I open the deployed page, ..it only gives me a simple line of text: you don't' have permission...etc.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4b0165d7-6462-842c-76ec-1a1f344fa51a
• Version Independent ID: 3b2c77ed-d9eb-cf20-0ace-908b88927e54
• Content: Create a Node.js web app in Azure | Microsoft Docs
• Content Source: articles/app-service/app-service-web-get-started-nodejs.md
• Service: app-service-web
• GitHub Login: @cephalin
• Microsoft Alias: cephalin;cfowler

[amanarneja]

@QiiLin Thanks for reporting! We are investigating and will get back to you.

[hihorika]

@amanarneja It seems that the zip file linked in this document doesn't include web.config.
The web.config is needed to execute iisnode and node.

So I think that the link has to be replaced by another link to a zip file which contains valid web.config`.

[amanarneja]

@hihorika Thank you for pointing this out! 👍
@cephalin - Can you take a look ?

[cephalin]

@hihorika Yes you're right. Tracking this issue internally at https://mseng.visualstudio.com/TechnicalContent/_workitems/edit/1207683.

[guillaumemeyer]

Use "--%" to escape the "|" in --runtime parameter

[SyntaxC4]

Possible dupe of #5957

[el-hult]

Love that you are on track with this. I spent 2-3 hours today trying to track down this bug. It is a big hurdle for us IIS-novices.

I changed to deployment from local git, and doing that makes the deploy-process automatically create the missing web.config. Until this is solved, anyone else could try that.

https://docs.microsoft.com/en-us/azure/app-service/app-service-deploy-local-git

[gowthamreddyvintha]

https://aspensurvey.azurewebsites.net/ZipDeploy
"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable." is giving me this error response. Is there any way to deploy my code base to webapp service from local machine

[cephalin]

The repo has now been updated to include the web.config file. #please-close

[uahgit]

Would love to actually see some documentation on how to properly config a web.config file, most documentation completely leaves out any mention of needing this with node.js apps on azure.

[cephalin]

@uahgit Yes. It's a bit of a blind spot for the zip push method because it doesn't generate the web.config in Azure automatically for you, whereas git deployment does. Kudu documentation however does have this information. See here: https://github.com/projectkudu/kudu/wiki/Using-a-custom-web.config-for-Node-apps

[akashirin]

I tried different settings in the web.config (including https://github.com/projectkudu/kudu/wiki/Using-a-custom-web.config-for-Node-apps and https://github.com/Azure-Samples/nodejs-docs-hello-world/issues/9 ). Nothing helps. Navigation to http(s)://.azurewebsites.net gives "You do not have permission to view this directory or page" after ZIP-deployment of the "nodejs-docs-hello-world-master" quickstart sample.

[GrantMeStrength]

This issue should not be closed yet - there still is no web.config created using the zip method, and so this walkthrough simply won't work. I've tested it myself, and only if you use the Git install method will the project actually work (took me two days of experimenting until I thought to click on the comments at the bottom of this document). Please either add a link to creating a web.config (which might not be trivial) or a link to the git install method.

[cephalin]

@GrantMeStrength I can't reproduce your error. The web.config file was added into the repository itself so it should be part of your zip file when you create it.

[GrantMeStrength]

I can to this page with an already created app, running locally, looking for how to publish it to Azure. So there was no web.config in my project. A note that explained web.config was required would have saved me a LOT of time.

[cephalin]

Based on your description, you have a scenario that varies from the quickstart. The quickstart is designed as a first-time experience in App Service, not generally for any app you have, and it works when you follow it as is written. But stay tuned because we're coming up with easier steps in the near future using az webapp up.

If you have any further issue with the quickstart experience itself, please open a new issue.

[GrantMeStrength]

Thanks! I can't find any other topics that cover moving the basics of moving a node.js app to Azure, so there is where I ended up.