Web App is not loading after deploying

Question

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.

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

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

Answer 1

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

Answer 2

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:

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.