Web App is not loading after deploying

3
votes

I have a working app service named "matanwebserver" over a subscription in Azure. This is a website that I am working on. I work with Visual Studio.

Now I created another Web App on the same subscription that I will use as an integration site so I can test my code before publishing to the production site. The name of the new Web App is "matanwebservertest". After publishing my project from Visual Studio to the new Web App, when I enter it's URL it seems like nothing happened, but it writes "Your App Service app is up and running".

What am I doing wrong?

Added some screenshots for a better understanding of the issue

  1. In Visual Studio I do right click on the web app which is called "MatanWebServer" and choose "publish". Then I choose the new web app that I just created on Azure portal which called "matanwebserertest", and publish successfully.

enter image description here

  1. This is the original (production) website. which its address is http://matanwebserver.azurewebsites.net

enter image description here

  1. After publish to the matanwebservertest web app, I expect to see a "copy" of the original site, but it seems like nothing is there.

enter image description here

5
azureazure-web-app-serviceazure-deploymentazure-app-service-plans
Have you check the project in the Kudu console? Your project exists or not? – Joy Wang-MSFT
@JoyWang It exists, I dragged a whole folder to the Kudu console, inside the rootwww and now it's a mess. Is there a way to go back ? – I.zv

5 Answers

3
votes

AFAIK, when publishing web application to Azure Web App via the publish wizard of VS, you would see the following similar logs:

Updating file (brucewebapp01\bin\AspDotNet-MVC-Website.dll)
OR
Adding file (brucewebapp01\Scripts\respond.js)

Your App Service app is up and running

Go to your app's Quick Start guide in the Azure portal to get started or read our deployment documentation.

It seems that your web app only picks up the hostingstart.html default page which is automatically created after you created your web app. The default documents for your web app look like this:

enter image description here

As Joy Wang commented, you'd better check your deployed contents under your matanwebserertest web app and compare them with the web contents under your production web app via KUDU or Azure App Service Editor or FTP tools to make sure that you have correctly deployed the proper web contents into your test web app. Details you could follow here.

Also, you could try to create a new web app and manually copy / drag the local published web contents into your new web app (D:\home\site\wwwroot) via KUDU or FTP tools to narrow this issue.

3
votes

I had the same issue, I fixed it by adding the command "dotnet YourArtifact.dll" command in:

mywebapp > Application Settings (Configuration) > General settings > Stack Settings -> Startup command

Adding startup command to Azure webapp

0
votes

To configure staging and production environment on Azure, use builtin feature "deployment slots". Follow these links to read more about deployment slots.

Documentation to Set up staging environments in Azure App Service

Video Tutorial to setup Azure WebSites - Deployment Slots for Staging Sites

Enabling Deployment Slots To Safely Deploy Applications To Azure App Service

0
votes

My issue was the .NET version I am using ASP.NET 4.6 for local builds but selected its runtime as 3.5

Went to Configuration > General Settings and changed the .NET Version to 4.8 (this should only work if you are using ASP.NET not Core) did the trick for me.

-1
votes

If the application version is .net core 3.1 and the publish profile is Linux then your "Startup Command" should be only "Application". Not "dotnet Application.dll"

Like This:

Startup Command: Application

settings image