Deployment issue in azure app service

MK 0 Reputation points
2023-03-28T07:11:38.5866667+00:00

Hi,

I am trying to deploy React & Angular based multifront end application using azure app services. Build & Release in azure devops is successful but in azure app services it is stating as mentioned below.

Your web app is running and waiting for your content

Your web app is live, but we don’t have your content yet. If you’ve already deployed, it could take up to 5 minutes for your content to show up, so come back soon.

I am facing this issue from past 2 days is this due to no command in configuration-general settings - start up command. if yes, what should be the command or it is due to some other issue... Need suggestion.

Thank you.

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
6,956 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. brtrach-MSFT 15,256 Reputation points Microsoft Employee
    2023-04-02T21:43:15.37+00:00

    It seems like your web app is live, but the content is not yet available. This could be due to a variety of reasons. One possible reason could be that the startup command is not set correctly.

    To set the startup command for your React & Angular based multifront end application, you can follow these steps:

    1. Go to the Azure portal and navigate to your web app.
    2. Click on the "Configuration" tab.
    3. Under "General settings", scroll down to the "Startup Command" section.
    4. Enter the command to start your application. For example, if you are using npm to start your application, the command could be "npm start".

    If the startup command is already set correctly, then the issue could be due to some other reason. You can check the logs for your web app to see if there are any errors or issues that are preventing the content from being displayed.

    You can also try restarting your web app to see if that resolves the issue. If the issue persists, you can try redeploying your application to see if that resolves the issue.

    I hope this helps! Let me know if you have any other questions.

    0 comments No comments